-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Strip apollo directives #374
Conversation
@stubailo How are we on this one ? I need to have it merged in order to continue my work on the infinite pagination ... |
I'll start by rebasing 😉 |
7729d44
to
e1f9e0d
Compare
Rebasing done ✅ |
@amandajliu is working on a refactor of query transforming right now, to generalize it so that this code is better. |
Well, ok, ping me when the refactor is ready so I can work on this again ... |
This should be refactored on top of #412, I think @amandajliu can do it! |
@stubailo: can do it today |
e1f9e0d
to
1b95187
Compare
Started by rebasing ... |
@stubailo: done ✅ |
3a0d87b
to
d3f5482
Compare
just rebased again |
@stubailo any ETA for a merge here ? I need it merged to continue splitting the PRs and I need the overall feature quite fast. |
d3f5482
to
d6c0f0d
Compare
We need primitives to parse directives correctly and validate them properly.
apolloFetch more accepts an optional name string argument.
We ensure that no apollo directives stays in the documents (queries)
We build on the tested stripApolloDirectivesFromDocument to integrate at batching-level directive stripping.
A QueryTransform is functionally unpure though, so this new stripping has side effects!
d6c0f0d
to
c86d092
Compare
This prevented us from making the directive stripper work correctly.
It is not needed given the fact the transformer will do it for us...
Rebased and made some important fixes to bugs introduced by #463 |
I'm closing this because I'm not sure we need it anymore? Could reopen if we still do. |
TODO:
Linked to the work of #350