manager
manager copied to clipboard
refactor: [M3-8043] - Query Key Factory for Volumes
Description ๐
Refactors Volume Queries
Changes ๐
- Performs some slight organization ๐๏ธ
- Uses a query key factory for volume queries ๐ญ
- Addresses the "single object notation" breaking change in preportion for v5 (https://tanstack.com/query/v5/docs/framework/react/guides/migrating-to-v5#supports-a-single-signature-one-object)
Preview ๐ท
[!note] No UI changes
How to test ๐งช
- Verify all Volume create, update, delete work the same as the previously did
- Verify all automated testing for volumes pass
As an Author I have considered ๐ค
- [ ] ๐ Doing a self review
- [ ] โ Our contribution guidelines
- [ ] ๐ค Splitting feature into small PRs
- [ ] โ Adding a changeset
- [ ] ๐งช Providing/Improving test coverage
- [ ] ๐ Removing all sensitive information from the code and PR description
- [ ] ๐ฉ Using a feature flag to protect the release
- [ ] ๐ฃ Providing comprehensive reproduction steps
- [ ] ๐ Providing or updating our documentation
- [ ] ๐ Scheduling a pair reviewing session
- [ ] ๐ฑ Providing mobile support
- [ ] โฟ Providing accessibility support
Coverage Report: โ
Base Coverage: 81.82%
Current Coverage: 81.82%
Manually tested the Volumes functionality across the application and did not experience any issues. No issues with C/I pipelines. Overall it's a good refactor of the existing queries that will serve as an example for future refactors using the query key factory pattern.