fix: api error page #556
Merged
fix: api error page #556
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Before this PR, if we click on the 🔒 icon on the top right of the screen, the API error page will be shown instead of the lock screen even If I have the correct API credentials.
To solve this, I only give the condition of the lock screen more priority than the API error page.
The rest changes only for linting.
Related Issue
Not applicable.
Motivation and Context
How Has This Been Tested?
Manually clicking on the 🔒 icon will redirect you to the lock screen instead of the condition of API error page
Screenshots (if appropriate):
Not applicable.