Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Support extensions in GraphQLRequest (#1347, graphql/graphql-spec#976) #1356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
tyranron wants to merge 4 commits into master
base: master
Choose a base branch
Loading
from 1347-request-extensions

Conversation

@tyranron
Copy link
Member

@tyranron tyranron commented Oct 22, 2025 •
edited
Loading

Part of #1347

Synopsis

GraphQL September 2025 spec standardizes optional extensions field for implementation-specific details:

Juniper should be able to parse such implementation-specific details and provide them in juniper::Context during execution.

Solution

  • Add pub extensions: Ext field to GraphQLRequest, where Ext = Variables<S> by default. This way, user code could define any structured extensions as it desires, while by default the code will just work.
    • in juniper_actix
    • in juniper_axum
    • in juniper_hyper
    • in juniper_rocket
    • in juniper_warp
  • Wire these extensions to Context in GraphQLRequest::execute() method. (TODO: describe how)

Checklist

  • Tests are added
  • Documentation is added (including Book)
  • CHANGELOG is filled

@tyranron tyranron added this to the 0.18.0 milestone Oct 22, 2025
@tyranron tyranron self-assigned this Oct 22, 2025
@tyranron tyranron added enhancement Improvement of existing features or bugfix semver::breaking Breaking change in terms of SemVer k::api Related to API (application interface) k::refactor Refactoring, technical debt elimination and other improvements of existing code base feature New feature or request k::design Related to overall design and/or architecture labels Oct 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Labels

enhancement Improvement of existing features or bugfix feature New feature or request k::api Related to API (application interface) k::design Related to overall design and/or architecture k::refactor Refactoring, technical debt elimination and other improvements of existing code base semver::breaking Breaking change in terms of SemVer

Projects

None yet

Milestone

0.18.0

Development

Successfully merging this pull request may close these issues.

GraphQL spec September 2025

1 participant

AltStyle によって変換されたページ (->オリジナル) /