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
Having the possibility to persist arbitrary queries (in my opinion) is one of the main reasons people use persisted queries at the build time which is difficult to orchestrate and adds more work when migrating over GraphQL as a public API.
Proposal:
Enable modules to extend the validation rules of queries before they are persisted in order to create their own custom logic that applies best to their business use case.
The text was updated successfully, but these errors were encountered:
Having the possibility to persist arbitrary queries (in my opinion) is one of the main reasons people use persisted queries at the build time which is difficult to orchestrate and adds more work when migrating over GraphQL as a public API.
Proposal:
Enable modules to extend the validation rules of queries before they are persisted in order to create their own custom logic that applies best to their business use case.
The text was updated successfully, but these errors were encountered: