Skip to content
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

🐛 Optimize assessment fetching #1716

Merged
merged 4 commits into from
Feb 28, 2024
Merged

Conversation

ibolton336
Copy link
Member

@ibolton336 ibolton336 commented Feb 28, 2024

@ibolton336 ibolton336 added the cherry-pick/release-0.3 This PR should be cherry-picked to release-0.3 branch. label Feb 28, 2024
@ibolton336 ibolton336 marked this pull request as ready for review February 28, 2024 16:49
Copy link
Member

@sjd78 sjd78 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

visack is ok

Considering how more things are being fetched and processed in aggregate, it may be time to reconsider how the query hooks are structured. There is a lot going on here and it is not unit/integration testable. It's to keep in mind and work on in the near future as things will not get less complicated as we go.


if (fetchError) {
return <EmptyTextMessage message={t("terms.notAvailable")} />;
}

if (isFetching || isFetchingAssessmentsById) {
if (isFetching || isFetching) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if (isFetching || isFetching) {
if (isFetching) {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick/release-0.3 This PR should be cherry-picked to release-0.3 branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants