Merged
Conversation
|
@EzeanoroEbuka Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or 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
2 participants
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.
PR: Guard Decorator full Implementation
Closes #42
This PR introduces a clean and maintainable authorization system using Guards combined with custom Decorators.
Guards handle the runtime decision of whether a request should proceed (e.g. authentication, role/permission checks), while custom decorators allow developers to declaratively annotate controllers and route handlers with metadata (such as required roles, permissions, or public access flags). This keeps authorization logic out of business code and makes security requirements explicit and easy to audit.
Overview
Closes
Please review the implementation and test the endpoints via Swagger UI (
/api/docs).