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
I've been experimenting with the 1.0 release, which is really excellent! We are looking to use SpectaQL for our docs and the release is really timely as it allows us to do the customisation we want without forking (both themes and the data customisation are exactly what we wanted). Thank you for all the great work!
I've spotted a few changes/issues from the previous version when we run it on our schema. I'll create separate tickets for each, but to start: I noticed you now capitalize the first letter of the query name automatically here:
I've been experimenting with the 1.0 release, which is really excellent! We are looking to use SpectaQL for our docs and the release is really timely as it allows us to do the customisation we want without forking (both themes and the data customisation are exactly what we wanted). Thank you for all the great work!
I've spotted a few changes/issues from the previous version when we run it on our schema. I'll create separate tickets for each, but to start: I noticed you now capitalize the first letter of the query name automatically here:
spectaql/src/spectaql/generate-graphql-example-data.js
Line 54 in eba011e
For us this isn't ideal as we use snake_case query names so it looks a bit odd and is inconsistent with what shows up on the row below:
Is there a reason for forcing to a capital letter? Any chance of putting it back how it was or making it optional?
The text was updated successfully, but these errors were encountered: