Fix: Use the correct description text when throwing a ForbiddenException #377
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
klaasdellschaft
force-pushed
the
fix-forbiddenexception-description
branch
from
e447236 to
177b680
Compare
|
Hi @AnuradhaSK could you provide a review for this pull request? I'm asking you because you reviewed and merged the last three successful pull requests in this repository. If you cannot provide review, could you recommend me how to proceed so that my open pull requests get reviewed, and hopefully merged? (There are two more open pull requests submitted by me: #378 and #376 ) Thanks, |
lashinijay
approved these changes
Mar 3, 2025
nilasini
approved these changes
Mar 7, 2025
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.
Purpose
Fix: Use the correct description text when throwing a
ForbiddenException