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

Adding loading step to customize query selection #48

Conversation

robertandremitchell
Copy link
Collaborator

PULL REQUEST

Summary

This adds a loading step to the customize query step to prevent from getting ahead of the db load.

I think the only other open questions I had:

  • do we want the customize query button unclickable until an actual selection is made? If you click the button, it just takes you to a blank version of the page, which could be a little confusing if the user does think they made a selection.
Screenshot 2024-10-23 at 10 50 20 AM
  • is Social Determinants of Health supposed to be broken? Getting this error:
    No results found for query: Social Determinants of Health

I can open up a ticket to look more closely at it, but I wasn't sure if this was a known bug or if anyone knew offhand why it may now be broken.

Related Issue

Fixes #47

Acceptance Criteria

Please copy the acceptance criteria from your ticket and paste it here for your reviewer(s)

For frontend PR’s - include a description (including anything that’s out of scope) for what you want the designers to review

  • ex: “Check out the whitespace on the page, as well as the dropdowns in the form. Here is the corresponding Figma link. You can ignore everything else. Also, the button at the bottom doesn’t work now”

Additional Information

Anything else the review team should know?

Checklist

  • If this code affects the other scrum team, have they been notified? (In Slack, as reviewers, etc.)

Copy link
Collaborator

@fzhao99 fzhao99 left a comment

Choose a reason for hiding this comment

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

For the good of the order, the proper UX pattern for this would be to implement a loading skeleton. Since we have enough to know what the overall layout of the page would be / on the happy path the page would load on the order of seconds, having a intermediary loading state that mimics the final result helps with user orientation / perceptions of load times.

Recognizing that's a bit out of scope though, my opinion is just having customize query disabled w/o the loading overlay is fine. Having the spinner blink through the loading state is a bit jarring for what we need at this point.

I think while you're at it, gating customize query selection until a valid option is selected is a good add!

Copy link
Collaborator

@fzhao99 fzhao99 left a comment

Choose a reason for hiding this comment

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

lgtm!

@robertandremitchell
Copy link
Collaborator Author

@robertandremitchell robertandremitchell merged commit b22b84d into main Oct 23, 2024
4 checks passed
@robertandremitchell robertandremitchell deleted the rob/47-customize-query-navigation-can-get-ahead-of-db-read branch October 23, 2024 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Customize query navigation can get ahead of db read
2 participants