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.
feature: improve speaker list activity count on select #998
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
Uh oh!
There was an error while loading. Please reload this page.
feature: improve speaker list activity count on select #998
Changes from all commits
74a304938164eaFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
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.
getSelectedSubmittersActivityCountis a near-verbatim copy ofgetSelectedSpeakersActivityCount— same 70 lines, same logic, only the state key (currentSummitSubmittersListStatevscurrentSummitSpeakersListState) and the endpoint segment (submittersvsspeakers) differ. Any fix applied to one (e.g. the filter-change staleness above) has to be manually mirrored in the other.Consider extracting a shared action factory parameterized by state key and endpoint, and having both exports delegate to it.
@santipalenque
Uh oh!
There was an error while loading. Please reload this page.
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 agree , but this would be an improvement to the whole submitters vs speakers action file, imo out of scope for this task and rather work on it on a separate ticket
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.
componentDidUpdateonly triggersgetSelectedActivityCount()whenselectedCountchanges, butgetSelectedSpeakersActivityCount(and the submitters variant) passes the active filters to the API. If the user has speakers selected and then changes a filter (track, selection plan, activity type, etc.), the list reloads and the filter context changes — butselectedCountstays the same, so no refresh fires. The displayed activity count will be stale until the next selection change.Consider also diffing the active filter fields from
prevProps[subjectPropKey]vs the current ones and triggering the count fetch when any of them changes.@santipalenque
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 is not true @smarcet . REQUEST_SPEAKERS_BY_SUMMIT called when filters change is resetting the selectedCount, so the selectedActivityCount will reset too
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.