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

SPIKE: Purge a specific query's cache by submitting a mutation #92

Open
bhardie opened this issue Jan 25, 2022 · 2 comments
Open

SPIKE: Purge a specific query's cache by submitting a mutation #92

bhardie opened this issue Jan 25, 2022 · 2 comments
Assignees
@markkelnar
Labels
needs: discussion Requires a discussion to proceed type: enhancement Improvements to existing functionality
Milestone
Query Caching

Comments

@bhardie
Copy link

bhardie commented Jan 25, 2022 •
edited
Loading

Questions to answer:

  • What do we need to know to be able to purge a specific query's cache?
  • Purge all cached data regardless of variables
  • Purge based on variable values
  • What level of complexity is required / what are the MVP features?
  • What level of complexity would be nice to have
@bhardie bhardie added this to the Query Caching milestone Jan 25, 2022
@bhardie bhardie changed the title As a site admin, I can purge a specific query's cache As a site admin, I can purge a specific query's cache by submitting a mutation Feb 8, 2022
@bhardie bhardie changed the title As a site admin, I can purge a specific query's cache by submitting a mutation SPIKE: Purge a specific query's cache by submitting a mutation Feb 8, 2022
@markkelnar
Copy link
Contributor

Would we want to purge by:

  • queryId with/without variables?
  • url parameters with/without variables?
  • Post/node id?
  • Content type (posts, tags, etc)?
  • purge all?

@jasonbahl
Copy link
Collaborator

This is worth working on but needs some better acceptance criteria.

@jasonbahl jasonbahl added type: enhancement Improvements to existing functionality needs: discussion Requires a discussion to proceed labels Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@markkelnar markkelnar

Labels
needs: discussion Requires a discussion to proceed type: enhancement Improvements to existing functionality
Projects
None yet
Milestone
Query Caching
Development

No branches or pull requests
3 participants
@markkelnar @bhardie @jasonbahl