feat(packages/gqty): support operationName #1276
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
vicary
changed the title
vicary
force-pushed
the
feat/operation-name
branch
2 times, most recently
from
73fc27f to
41d7772
Compare
vicary
force-pushed
the
feat/operation-name
branch
from
41d7772 to
3ac9ff1
Compare
vicary
force-pushed
the
feat/operation-name
branch
2 times, most recently
from
902fb48 to
1fbba64
Compare
vicary
force-pushed
the
feat/operation-name
branch
from
4fdf577 to
9221c0e
Compare
vicary
force-pushed
the
feat/operation-name
branch
from
d84be9c to
d26adc9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a preparation step for #876, react changes will be done in another PR.
Quite a patchwork at the moment, I can't think of a way to proper scope selections with the current scheduler/interceptor design.
I may introduce a new fluent API at client level accessor/proxy in the future, e.g.
client.withOptions({ operationName }).query.hello.