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
{{ message }}
Repository navigation
Backwards compatibility issues with DIRECTIVE_DEFINITION location on older versions of graphql #4479
the standard @deprecated directives now allows itself to be on DIRECTIVE_DEFINITION
However if this modern schema is then represented to some other consumer who is on a graphql version that is older and this is very common right now) then they consumer will choke on the schema
To Reproduce
Print a schema on latest graphql-java (say 0.0.0-2026-03-18T00-52-57-e53ab1a. Consume that schema on a client running an older version of graphql-java (say 25.0)
** Design concerns **
Normally the version of graphql-java is localised to the running instance and hence this additive change would be ok but schema printing and introspection are ways in which schema can leave the runtime version of the server and need to be run on older versions.
I think there should be a "predicate" / "switch" mechanism that allows older versions (1 back say) of schema to be printed / produced.
Activity