Too bad it was decided to become so Apollo-dependent. It will cause issues if another client library pops up and uses a different persisted query mechanism.

It's not Apollo dependent at all. People have always been able to build out a PreparsedDocumentProvider and so could have done this before hand.

This adds an abstract class PersistedQuerySupport that can be the basis for implementations. I happened to put in an Apollo one to be useful to the VERY popular Apollo JS client.

We have some Apollo specific code already like graphql.execution.instrumentation.tracing.TracingSupport based on it being a de facto standard at the time. This the same thing.

Some one can create new implementations, either from first principles or from extending the PersistedQuerySupport starting point.

Honestly I am not sure on the tone of your reply. At best it seems unappreciative and snarky.