-
Notifications
You must be signed in to change notification settings - Fork 43
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
🐛 Disabling useFetchCache query if RWX_SUPPORTED=false #1963
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1963 +/- ##
==========================================
+ Coverage 39.20% 41.98% +2.78%
==========================================
Files 146 175 +29
Lines 4857 5630 +773
Branches 1164 1409 +245
==========================================
+ Hits 1904 2364 +460
- Misses 2939 3145 +206
- Partials 14 121 +107
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mguetta1 - Can you provide some context for this change? Is there an issue or ticket for this? At face value it looks ok, but I'm not sure how the isRWXSupported
flag is meant to interact with the loading spinner.
Hi @sjd78, @dymurray |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The loading state seems the consequence of the query being active. IMHO if the entire feature is disabled we should disable the query as well.
React query uses enable
flag for this purpose. We use in several places i.e. here.
Signed-off-by: Maayan Hadasi <[email protected]>
Signed-off-by: Maayan Hadasi <[email protected]>
Done in ee7c7a2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! If there will be another use case for useFetchCache
then we can always refactor.
@mguetta1 please edit the title to better reflect the fix. |
Resolves: https://issues.redhat.com/browse/MTA-3699