feat: added User Role System feature #43
Open
+435
−581
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.
What does this PR do?
Implement a user role system that assigns different roles (admin, editor, user) with specific permissions for managing blog content.
This feature will allow for better content management, enabling specific users to edit or delete posts while restricting access for regular users.
Fixes #35
Type of change
Implemented roles such as Admin, Editor, and User.
Added role definitions in the user model to ensure clarity and maintainability.
Implemented middleware to enforce role-based permissions on various endpoints.
Only Admin users can perform actions like creating, editing, or deleting blog posts.
Editors can edit existing posts but cannot delete them.
Regular Users can only view posts.
Updated the user interface to reflect role-specific actions.