graphql / graphql/graphiql

When using large schema files, you can not jump quickly every time

Open
#2,985 2 comments 2 reactions 0 assignees View on GitHub
bug graphiql
Dominant language
TypeScript
Stars
16.9k
Forks
1.9k
Avg merge
22h 45m
Merged PRs (30d)
70

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

I'm doing work about [GraphQL API of shopify](https://shopify.dev/api/admin-graphql) on **VsCode**.
However, the graphql definition of shopify is very large, resulting jump to the definition is slow.
At first, I thought it was caused by not setting the jump related index.
Later, I found that I can jump very quickly when the first time.
Therefore, I thought it was because the large file opened after the jump caused the plug-in to get stuck.
I hope to cache this large file in the background instead of reloading it every time.

### Expected Behavior

Jump to the definition quickly

### Steps To Reproduce

Use the definition of [shopify's graphql API](https://shopify.dev/api/admin-graphql) , about `60,000` lines

### Module pattern

- [ ] graphiql-umd
- [ ] graphiql-esm
- [x] graphiql-commonjs

### Environment

```Markdown
- GraphiQL Version:
- OS: Windows10
- Browser:
- Bundler:
- `react` Version:
- `graphql` Version:
```

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.