-
Notifications
You must be signed in to change notification settings - Fork 162
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
Incorrect work with extend
in Query and Mutation
#159
Comments
extend
for Queryextend
in Query and Mutation
Thanks for opening an issue @VasiliKubarka ! Can you take a look at my comments here: #132 (comment). Would #1 qualify as a reproduction for what you're seeing? If so, I'll mark this is a duplicate of #132. If not, can you please provide a reproduction? Relates to #132 |
@justinanastos Hello, thanks for reply, don't think that it's the same behavior that I faced.
For example in both versions but as I described before, client typeDefs has been shown in So can you please describe, what is expected behavior for reflection client typeDefs in devTools? |
We've added all local state to GraphiQL with v2.2.0. This works for |
I've updated to v2.2.0 and it does not show the local schema (using it together with apollo-client@2.5.0). Can anyone confirm that the local schema shows up in the Documentation Explorer in v2.2.0? |
Can you give any more details @raedle ? I checked out the full stack tutorial, ran the apps in and the inclusion of those I see the local schema extensions in the Documentation Explorer and there are no warnings given about either the local fields or the |
Thanks @justinanastos for your quick response. I tried the fullstack tutorial, but even with this one I don't see the local schema in the Documentation Explorer. I even installed the Apollo Client Dev Tools extension on a clean Google Chrome account, but still no local schema. I'm using Google Chrome Version 72.0.3626.119 and the Apollo Client Dev Tools v2.2.0 from the Google Marketplace. |
@raedle Are you on the latest version of the fullstack tutorial with the latest dependencies installed in To check:
What do you see? |
It works after updating both packages to v2.5.1. In my own project, I had both packages at v2.5.0, and the fullstack was on apollo-client@2.5.0-alpha.10 and react-apollo@2.4.0-alpha.3. Thanks you! |
Thank you @raedle ! There was a change going from rc2 → rc3 that changed how the Apollo Client DevTools access Apollo Client's local |
Hello all! Have few questions/bugs/features with
extend
keyword in version2.1.5
Queries declared with
![image](https://user-images.githubusercontent.com/19685464/49995644-cc757c00-ff9d-11e8-90d8-a9921af7f9e7.png)
![image](https://user-images.githubusercontent.com/19685464/49995648-d1d2c680-ff9d-11e8-8213-6719c956f19e.png)
extend
not seen in devtoolswhen locally try to extend existing queries from server, have error
Must provide schema definition with query type or a type named Query.
can we remove this check or add functionality to work when all queries extends Query?
steps to reproduce:
result error: Must provide schema definition with query type or a type named Query.
but code is valid and works well
I can not create
type Query
without extending because it breaks validationsAny thoughts?
The text was updated successfully, but these errors were encountered: