Repository navigation
fix(solid-query/useMutationState): recompute the result when the filters or the 'queryClient' change - #12231
fix(solid-query/useMutationState): recompute the result when the filters or the 'queryClient' change#12231sukvvon wants to merge 1 commit into
Conversation
…ers or the 'queryClient' change
|
View your CI Pipeline Execution ↗ for commit 3b4b9e8
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview1 package(s) bumped directly, 23 bumped as dependents. 🟩 Patch bumps
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
size-limit report 📦 |

🎯 Changes
useMutationStatecomputed its result once and afterwards only on mutation cache events, so changing thefilters(orselect) or thequeryClientkept returning the previous result until the next mutation event.replaceEqualDeep.queryClient.✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact
Summary by CodeRabbit
Bug Fixes
useMutationStateso mutation results update when filters or the supplied query client change.Tests