Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch to user defined cache keys #56

Closed
jaydenseric opened this issue Feb 16, 2021 · 0 comments
Closed

Switch to user defined cache keys #56

jaydenseric opened this issue Feb 16, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@jaydenseric
Copy link
Owner

Currently, cache keys are a hash of the fetch options for the GraphQL operation.

A much simpler system is to allow users to define an arbitrary cache key for a GraphQL operation. This will result in a smaller, easier to understand API and a smaller bundle size without the fnv1a dependency.
@jaydenseric jaydenseric added the enhancement New feature or request label Feb 16, 2021
denisp22 added a commit to denisp22/graphql-react that referenced this issue Jul 27, 2023
@denisp22
Reorganize the file structure and replace the entire API.
6e9a2d1 
Also removes Babel and related dependencies and config. Fixes jaydenseric/graphql-react#24 , fixes jaydenseric/graphql-react#53 , fixes jaydenseric/graphql-react#55 , and fixes jaydenseric/graphql-react#56 .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jaydenseric