You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to have the dev tools appear when in non prod mode without being forced to use connectToDevTools = true
when dev tools do appear the queries disappear instantly but the mutations stay in place and the cache is functional.
Actual outcome:
I have to add connecToDevTools = true in two place. one in our subscription service and one in our apollo service/module
How to reproduce the issue:
I am unsure of the problem so I do not know the reproduction steps.
Desktop (please complete the following information):
OS: Winows 10 Pro 10.0.19043
Browser: Chrome
Browser version 98.0.4758.82
Extension version 4.0
UI:
Angular: 10.2.4
Apollo Client: 3.3.7
Server:
Apollo Server Core: 2.21.2
NestJS Core: 7.0.9
GraphQL: 15.3.0
We are instantiating new InMemoryCache(options) in 2 places in the UI.
unsure if this might be the concern.
our subscription service:
and our GraphQL Module:
this is the build options for Angular:
The text was updated successfully, but these errors were encountered:
Intended outcome:
Trying to have the dev tools appear when in non prod mode without being forced to use connectToDevTools = true
when dev tools do appear the queries disappear instantly but the mutations stay in place and the cache is functional.
Actual outcome:
I have to add connecToDevTools = true in two place. one in our subscription service and one in our apollo service/module
How to reproduce the issue:
I am unsure of the problem so I do not know the reproduction steps.
Desktop (please complete the following information):
UI:
Angular: 10.2.4
Apollo Client: 3.3.7
Server:
Apollo Server Core: 2.21.2
NestJS Core: 7.0.9
GraphQL: 15.3.0
We are instantiating new InMemoryCache(options) in 2 places in the UI.
unsure if this might be the concern.
our subscription service:
and our GraphQL Module:
this is the build options for Angular:
The text was updated successfully, but these errors were encountered: