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
Is the underscore necessary?
I am processing the resulting data in JavaScript with an existing code, based on camelCase data.
There was a different GraphQL server before. Now I am merging things together with your package and encountered the problem.
The text was updated successfully, but these errors were encountered:
Hey @donni106 , We underscore because that's the convention in Ruby when parsing GraphQL results. I can see the usecase for non-underscored results though, I can look into putting some sort of optional functionality together soon. Or, if you have time, feel free to PR :)
It would be nice, if we could find an optional way.
For now, I am transforming the keys with deeply renaming them in the frontend before accessing the resulting data.
This fell off my radar for a bit, I don't have a ton of time right now for non-functional or non-significant changes, but this should be an easy PR if anyone wants to add a camelCase config option.
Aliases are working fine. I can rename things in my query. But the bad thing is, that in the result everything is snake_cased.
Is this line responsible for that?
graphql-remote_loader/lib/graphql/remote_loader/loader.rb
Line 156 in 6ee709b
Is the
underscore
necessary?I am processing the resulting data in JavaScript with an existing code, based on camelCase data.
There was a different GraphQL server before. Now I am merging things together with your package and encountered the problem.
The text was updated successfully, but these errors were encountered: