FIX Surchages query missing permission validation #6862
Closed
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.
Resolves #6634
Impact: breaking|critical|major|minor
Type: feature|bugfix|performance|test|style|refactor|docs|chore
Issue
Description of the issue this PR is solving, why it's happening, and how to reproduce it. This may differ from the original ticket as you now have more information at your disposal.
Solution
Breaking changes
If you have a breaking changes, list them here, otherwise list none.
**Yes Following
We import the checkPermission function from your permissions library. You should replace 'your-permissions-library' with the actual name of your permissions library.
We check if the user has the necessary read permission for surcharges using checkPermission(user, 'surcharges:read'). You should replace 'surcharges:read' with the specific permission string or identifier used in your
If you're solving a UIX related issue, please attach screen-caps or gifs showing how your solution differs from the issue.
Examples of breaking changes include changing file names, moving files, deleting files, renaming functions or exports, or changes to code which might cause previous versions of Reaction or third-party code not to work as expected.
Note any work that you did to mitigate the effect of any breaking changes such as creating migrations, deprecation warnings, etc.
Testing
More detail for what each of these sections should include are available in our Contributing Docs.