TM4J-17231:fixing rovo with gemini #441
Draft
vmrvictor wants to merge 1 commit into
Draft
Conversation
…but is a number that is optional and nullable (nullish is not an option)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
so that folderId is not an object but is a number that is optional and nullable (nullish is not an option)
Goal
Rovo (with gemini) is not working with our actual schemas (nullish is not supported)
Design
avoid using nullish in our objects, decided not to use our own objects when we can use directly types (making our api schemas simpler)
Changeset
changing folder to be folderId (number.optional.nullable)
Testing
running manually on claude and rovo