fix: global search filters access check #1816
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 |
sagarnaikjuspay
added
analytics
S-waiting-on-review
gitanjli525
approved these changes
Nov 27, 2024
kanikabansal-juspay
approved these changes
Nov 27, 2024
JeevaRamu0104
approved these changes
Nov 27, 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
checking if the user has a acess to view rhe filetrs suggestions on global search
Motivation and Context
How did you test it?
if the uer doesn't have a acess he should be shown a suggestions for filters selected
Where to test it?
Checklist
npm run re:build