@homebound/graphql-id-linter
Advanced tools
According to apollo-client's [issue 2510](https://github.com/apollographql/apollo-client/issues/2510), the apollo client really, really wants you to include `id`s in every query that touches a type, so that it can maintain its cache.
According to apollo-client's issue 2510, the apollo client really, really wants you to include ids in every query that touches a type, so that it can maintain its cache.
In theory this is getting fixed in apollo-client 3.0-beta, but always returning id is probably not a bad idea anyway.
Credits, this is a ~80% copy/paste of Cecchi's solution on this comment.
npm install --save-dev @homebound/graphql-id-linter
Include it in your graphql-codegen.yml:
schema: ./schema.json
documents: src/**/*.graphql
generates:
src/generated/graphql-types.tsx:
plugins:
- "@homebound/graphql-id-linter"
FAQs
Unknown package
We found that @homebound/graphql-id-linter demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 34 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.