Skip to content

Conversation

@markkelnar
Copy link
Contributor

When smart cache object cache is enabled to store results of queries, do not get/store mutation requests.

Fixes #196

markkelnar and others added 2 commits July 24, 2023 08:16
@markkelnar markkelnar requested a review from jasonbahl July 24, 2023 16:28
@jasonbahl jasonbahl changed the title bug:Do not cache mutations to object cache results bug: do not cache mutations to object cache results Jul 24, 2023
Copy link
Collaborator

@jasonbahl jasonbahl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@markkelnar per your question in Slack, if the test here seems valid and beneficial, let's pull it in. If it's a flaky test or otherwise unhelpful, we can close that PR and move on.

Copy link
Collaborator

@jasonbahl jasonbahl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@markkelnar I merged the PR that fixes the tests and then merged main back into this PR and tests are still failing.

I investigated a bit and thought I had found a bug where the filter was returning nothing instead of the default filtered value.

However this didn't fix the issue.

The BatchQueryTest is still failing.

@jasonbahl
Copy link
Collaborator

@markkelnar I pushed up some more changes and got tests passing.

@jasonbahl jasonbahl self-requested a review July 26, 2023 14:43
@markkelnar markkelnar merged commit df2eb13 into wp-graphql:main Jul 26, 2023
@markkelnar markkelnar deleted the bug-mutation-should-not-cache branch July 26, 2023 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Mutations should not be cached

2 participants