-
Notifications
You must be signed in to change notification settings - Fork 55
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
Related attribute __typename and name are different when used GraphQL API #304
Comments
Checking |
@TaniaUdomsri I'm trying to reproduce your issue but I can't get to the state with mixed types you provided.
Response
|
Hi @cyp3rius, Thanks for taking a look at the issue. Yes, this is still happening. I understand this is a super weird bug. I'd like to point out this is only happening while using Apollo's |
So I think the difference and possible issue might be somewhere in the Apollo hook itself, some kind of configuration or properties of it. Have you played a bit with it? |
I've been trying to use useLazyQuery instead to wait for other queries and components to finished with no luck. Not sure what else to look for or where to start in this case. We have been using it for other queries for Strapi without any issues. Any advice? |
Hi, I'm not using the hook but the This option
as value in the option object, fixed this problem. To be honest I haven't figured it out yet why this happen, I just have some thoughts. Hope this help |
I have a few navigation items that have incorrect
__typename
andname
when used GraphQL API. I'd say 3 out of 8 items are incorrect. For example, the item below has Content type Page and Entity Page layouts.However, when queried from the frontend. It returned as
__typename
Foundation andname
Inclusivity. This attribute is from another navigation item.Here is the query I use:
Anything I should look into to fix this issue? Note, I have put navigation above graphQL in plugin config.
The text was updated successfully, but these errors were encountered: