You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These are bugs that were discovered during the initial testing process. I want to keep this here to prove the effectiveness of the original Sudograph tests, and of automated testing as a worthwhile endeavor.
JSON scalars were completely broken for candid serialization
Updating the nullable side of a one-to-one relationship should not be allowed...basically we need to implement foreign key constraints
Leaving out input did not allow object type information to be initialized in the database (relation one?)
Leaving out input did not allow object type information to be initialized in the database for relation many
Made me rethink throwing an error if the offset it too big, now gracefully returns empty (I think that is the better choice)
or was not working correctly, if there is nothing in the or then I think it should return true, not false
ors were being or'd within the field input thing, we needed to get rid of the flat_map
read_input was not returning empty read inputs when relation one had no values inside
Searching for null relations doesn't work properly
I forgot to add startsWith and endsWith to the search within selection sets in Sudograph generate
Search within relation sets was pretty broken...no null values were allowed
The text was updated successfully, but these errors were encountered:
These are bugs that were discovered during the initial testing process. I want to keep this here to prove the effectiveness of the original Sudograph tests, and of automated testing as a worthwhile endeavor.
The text was updated successfully, but these errors were encountered: