-
Couldn't load subscription status.
- Fork 712
Persist dismissing the OTLP unsecured message bar #5465
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
Conversation
| <Authorized> | ||
| @if (_showUserProfileMenu) | ||
| { | ||
| @if (_showUserProfileMenu) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only include AuthorizeView on the page if the user profile should be displayed (which means the auth mode needs to be a certain value).
This avoids the need to include various authz services in tests.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
729a469 to
8cb94d0
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Description
Running the dashboard without OTLP auth will display a warning message bar. The message bar can be dismissed, but it reappears if the browser is refreshed.
It is annoying to repeatedly show the message to a user who has already seen the warning. They either have to close the message every time, or accept it is always visible.
This PR:
Note that the warning displayed in console logs on startup isn't impacted. It's always displayed.
Checklist
<remarks />and<code />elements on your triple slash comments?