-
Notifications
You must be signed in to change notification settings - Fork 14
Issues: wp-graphql/wp-graphql-smart-cache
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
The plugin has stopped serving queries from disk cache on initial page load
needs: reproduction
This issue needs to be reproduced independently
#290
opened Aug 16, 2024 by
WintersInstruments
feat: seperate Requires a discussion to proceed
type: enhancement
Improvements to existing functionality
max-age
and s-maxage
needs: discussion
#280
opened Apr 26, 2024 by
moonmeister
Automate Releases (Implement Changesets or other applicable solutions)
type: enhancement
Improvements to existing functionality
#274
opened Feb 15, 2024 by
jasonbahl
Feature: Support for "global" Fragments
type: enhancement
Improvements to existing functionality
#276
opened Feb 12, 2024 by
jasonbahl
Allow modification of persisted queries but not the query string itself
status: actionable
Ready for work to begin
#259
opened Sep 12, 2023 by
ChrisWiegman
Introduce UI Elements to show when graphql_documents will expire
type: enhancement
Improvements to existing functionality
#245
opened Aug 9, 2023 by
jasonbahl
Increase PHPstan strictness level
scope: build scripts
Automating task runners and compilation processes
type: enhancement
Improvements to existing functionality
#238
opened Jul 31, 2023 by
markkelnar
7 of 8 tasks
Track and Purge Connections
effort: high
More than a week
type: enhancement
Improvements to existing functionality
#233
opened Jul 21, 2023 by
jasonbahl
Update Actions and Filters to be named consistenty
effort: low
Around a day or less
good first issue
Issue that doesn't require previous experience with codebase
status: actionable
Ready for work to begin
type: enhancement
Improvements to existing functionality
#231
opened Jul 14, 2023 by
jasonbahl
Prevent Persisted Queries from saving if arguments are used without variables
effort: med
Less than a week
type: enhancement
Improvements to existing functionality
#224
opened Jun 20, 2023 by
jasonbahl
Unable to purge post after changing status from Ready for work to begin
type: bug
Issue that causes incorrect or unexpected behavior
Draft
to Published
status: actionable
#223
opened Jun 14, 2023 by
predaytor
Tracking of meta updates should be opt-in instead of opt-out
compat: breaking change
This is a breaking change to existing functionality
type: enhancement
Improvements to existing functionality
#218
opened May 5, 2023 by
jasonbahl
Exclude specific queries/mutation from being served from the object cache
has: workaround
A temporary workaround has been provided
type: enhancement
Improvements to existing functionality
#182
opened Nov 17, 2022 by
eplanne
Purging should happen async
impact: high
Unblocks new use cases, substantial improvement to existing feature, fixes a major bug
type: enhancement
Improvements to existing functionality
#165
opened Aug 18, 2022 by
jasonbahl
Invalidate caches when settings (options) change
type: enhancement
Improvements to existing functionality
#158
opened Jul 26, 2022 by
jasonbahl
1 task
As a developer, I would like to be able to filter the GraphQL Query Cache Key
type: enhancement
Improvements to existing functionality
SPIKE: Purge a specific query's cache by submitting a mutation
needs: discussion
Requires a discussion to proceed
type: enhancement
Improvements to existing functionality
As an admin user, I would like to know which saved Query Document(s) contain breaking changes when the GraphQL Schema has been changed
scope: graphiql
issues related to the GraphiQL IDE integration
As an admin user, I would like to be able to identify which GraphQL Documents were generated from "Automated Persisted Queries"
scope: graphiql
issues related to the GraphiQL IDE integration
As an admin user, I would like to organize GraphQL Documents in my own "collections" for future reference
scope: graphiql
issues related to the GraphiQL IDE integration
As an admin user I would like to be able to delete GraphQL Documents
scope: graphiql
issues related to the GraphiQL IDE integration
I would like to be able to store a description about the document
scope: graphiql
issues related to the GraphiQL IDE integration
I would like to be able to modify the allow/deny grant (allow queries to be executed or blocked)
scope: graphiql
issues related to the GraphiQL IDE integration
I would like to be able to modify the expiration (max-age)
scope: graphiql
issues related to the GraphiQL IDE integration
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.