fix: unauthorised page issue #1588
Merged
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
|
Review changes with SemanticDiff. |
JeevaRamu0104
added
the
S-blocked
Riddhiagrawal001
approved these changes
Oct 14, 2024
kanikabansal-juspay
approved these changes
Oct 14, 2024
github-actions
bot
added
Closed
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.
Type of Change
Description
Facing unauthorised page on switching the merchant and profile in the user page.This is due to because the screen state is not set to loading during the user role api is called.
Now screen state is set to loading while calling the user roles api.
Motivation and Context
Screen.Recording.2024-10-10.at.1.43.28.PM.mov
How did you test it?
unauthorised page shouldn't appear during org or merchant or profile switch.Check payment page
Where to test it?
Checklist
npm run re:build