You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Page spinner does not wait for entity detail to be fully rendered before disapearing. This results in the spinner disapearing right after a search result is clicked and then presenting a blank white page with a generic icon until all the component can be fully rendered.
To Reproduce
Steps to reproduce the behavior:
Enter a name in search box
Click on a name, the spinner will briefly appear.
then wait another 10-XX seconds for the entity detail to render
Expected behavior
You click a name, spinner starts and when it dissapears the user is immediately presented with the entity detail for the result they clicked on.
Additional context
I'm 90% sure this bug was introduced when we either included the graph component, or when we broke the graph components out to a separate project/repo.
The text was updated successfully, but these errors were encountered:
found the issue, it's not the graph api request. it's the withRelated=true part of the main entityId request. I have a fix for the UI spinner waiting until the request is actually complete, as for the speed of the request response, that's a separate issue.
Describe the bug
Page spinner does not wait for entity detail to be fully rendered before disapearing. This results in the spinner disapearing right after a search result is clicked and then presenting a blank white page with a generic icon until all the component can be fully rendered.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
You click a name, spinner starts and when it dissapears the user is immediately presented with the entity detail for the result they clicked on.
Additional context
I'm 90% sure this bug was introduced when we either included the graph component, or when we broke the graph components out to a separate project/repo.
The text was updated successfully, but these errors were encountered: