apollographql / apollographql/apollo-tooling
Support service projects better in VS Code
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 460
- PR merge metrics
- No merged PRs in 30d
Description
**Intended outcome:**
I expected it to report some level of success like my client project does. Maybe something like:
```
------------------------------
🚀 Apollo GraphQL v1.5.0
------------------------------
✅ Service Loaded!
🏷 Schema Tag: current
📈 Number of Types: 22
------------------------------
```
**Actual outcome:**
```
------------------------------
🚀 Apollo GraphQL v1.5.0
------------------------------
```
**How to reproduce the issue:**
It appears to halt on simply adding the service property. But this is my exact config:
```
module.exports = {
service: {
localSchemaFile: './src/generated/schema.graphql'
}
};
```
Despite no actual error being raised, I see no apparent result. I guess I expected, at a minimum, to see autocomplete in the `schema.graphql` file. Maybe I'm just expecting the wrong results.
**Versions**
V1.5.0
Contributor guide
Research direction
Reproduce the report in VS Code using the shown service.localSchemaFile configuration and inspect the existing service-project handling; no repository file or test is named in the issue. Done means the configuration produces a clear service result and the expected schema.graphql experience, with behavior agreed for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100