CamelCase named fields are missing in GraphQL explorer and introspection

We are consistently experiencing the issue when fields defined in our content types, both in Slices and regular ones, are missing from GraphQL introspection result and GraphQL explorer. We tried publishing pages after changes, saving, resaving with no success.

GraphQL is not very useful without the schema/introspection and this kind of inconsistent behavior makes GraphQL implementation not reliable.

EDIT: After reading other topics I verified that missing fields are indeed using "camelCase". Is there any reasoning behind "camelCase" fields names not being supported in GraphQL and dropped silently? We have already a bunch of content published under the type, so we can't really change the field names. Are there any plans to address this issue?

3 Likes