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

[LIBSEARCH-61] Investigate ways to overcome late loading of profile data #504

Conversation

erinesullivan
Copy link
Contributor

Overview

Profile data is loaded asynchronously after the initial load of Search data (datastore information, filters, etc.). If a user is authenticated with co-sign, but the Search UI doesn't know if this yet, this would cause unnecessary rerouting to login.

The app has been updating to synchronously run all setup functions before running renderApp. The Log in/out button in the header also no longer shows until the profile state has finished loading. All other components using the profile state have been modified to bring in the necessary data instead of the full object.

This pull request resolves LIBSEARCH-61.

Testing

  • Make sure the PR is consistent in these browsers:
    • Chrome
    • Firefox
    • Safari
    • Edge
  • Run accessibility tests:
    • WAVE
    • ARC Toolkit
    • axe DevTools
  • Look through the site and check if everything still works.

…s been loaded. Destructuring `state.profile` in `ActionsList` to only pass through the `status` string instead of the full `profile` object.
@erinesullivan erinesullivan self-assigned this Nov 14, 2024
@erinesullivan erinesullivan merged commit 7a995a0 into master Nov 14, 2024
7 checks passed
@erinesullivan erinesullivan deleted the LIBSEARCH-61-investigate-ways-to-overcome-late-loading-of-profile-data branch November 14, 2024 20:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant