apollographql / apollographql/apollo-client-devtools

Angular Apollo Dev Tools Issues

Open
#812 2 comments 1 reaction 0 assignees View on GitHub
🐞 bug
Dominant language
TypeScript
Stars
1.5k
Forks
172
Avg merge
10m
Merged PRs (30d)
8

Description

**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):**
- 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:
![image](https://user-images.githubusercontent.com/62255879/152706300-069d00c2-70ad-4d73-ba33-f99221412093.png)
and our GraphQL Module:
![image](https://user-images.githubusercontent.com/62255879/152706326-4396f02c-6900-4a84-976c-deb667023c81.png)

this is the build options for Angular:
![image](https://user-images.githubusercontent.com/62255879/152706384-c9c52a69-9704-4d43-91d6-4c7a90605735.png)

Contributor guide

Open the contributing guide

Research direction

Review the subscription service and GraphQL Module configurations, including the two InMemoryCache instantiations and connectToDevTools settings. Establish a reproducible non-production Angular case first; done means the dev tools appear without forcing the setting and queries remain visible while the cache continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, graphql, typescript
Domain
devtools, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.