Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[Discover] Refactor totalHits$ loading state handling to omit race conditions #196114
[Discover] Refactor totalHits$ loading state handling to omit race conditions #196114
Changes from 7 commits
3f08047
ce1ab00
5f6b405
b777be0
b36d6a1
8b4ae35
9795323
931aa13
b50e996
62b1fdd
4b6480f
2eef183
be3ae5f
91c587f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I think there was a good reason why the histogram was sending the
loading
status all this time. But I don't remember all the cases about that. Do you mind if we wait for @davismcphee review?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.
yes, let's wait, from what I've seen, it doesn't hurt keeping it, but on the other hand, I thought it's redundant
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.
As far as I can tell, as long as we're setting the loading state every time in
fetchAll
, I think this should be ok.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.
Maybe we should keep the previous
result
too?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.
I'm not sure about that, because I think if I send a
loading
, the previous result is not longer valid? So if we rely on a previous result somewhere we might change thisThere 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.
I'm also not sure it's needed, but we used to do it when setting the loading state in
use_discover_histogtam
too, so probably best to keep passingresult
for now. It would get rid of this conditional too (and the comment above doesn't apply anymore anyway).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.
You're both right, let's simplify the code ... done
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.
uncommenting the code can be very helpful to unterstand data fetching observables race conditions, I think it's worth keeping it here
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.
This could be helpful to debug at least a part of the staff you mention in #165192 (comment) @jughosta