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
Apologies for not submitting this issue while it was fresh in mind. Was working in the 'update-api' branch - to update query.py to reflect changes made in the mutations/ database structure. This was to able to retrieve data through graphiql (localhost:4000/graphql) and the UI. (Had mostly been working in with the database UI up to this point.)
While the webendpoint query was able to pull out the check_passes and metadata fields, strangely the githubendpoint query was not. After running through the debugger with Collin, we narrowed it down to an issue with the strawberry library not performing the second camelCase/snake_case conversion, causing either not found field errors or null results.
Since the webendpoint works, you may want to investigate the differences to see if there's another cause.
Also note - there likely needs to be some mutation refactoring - to take into consideration how the data is being used by the UI.
The text was updated successfully, but these errors were encountered:
Apologies for not submitting this issue while it was fresh in mind. Was working in the 'update-api' branch - to update query.py to reflect changes made in the mutations/ database structure. This was to able to retrieve data through graphiql (localhost:4000/graphql) and the UI. (Had mostly been working in with the database UI up to this point.)
While the webendpoint query was able to pull out the check_passes and metadata fields, strangely the githubendpoint query was not. After running through the debugger with Collin, we narrowed it down to an issue with the strawberry library not performing the second camelCase/snake_case conversion, causing either not found field errors or null results.
Since the webendpoint works, you may want to investigate the differences to see if there's another cause.
Also note - there likely needs to be some mutation refactoring - to take into consideration how the data is being used by the UI.
The text was updated successfully, but these errors were encountered: