refactor: move project filtering to server side #8102
Merged
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.
Signed-off-by: Alexander Matyushentsev AMatyushentsev@gmail.com
PR moves improve applications list page performance by moving project filtering to server-side. When a user adds the project filter then both list and stream API will reduce only project-related applications which significantly reduce browser CPU usage. The disadvantage is that use will see a loading indicator after changing project filter:
Screen.Recording.2022-01-05.at.2.37.30.PM.mov
I believe the loading indicator is acceptable in this case because typically end-users select the required project once and don't change it very frequently.