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.
Description
This pull request introduces a new feature allowing achievements to be revoked from users. It includes updates to the documentation, the addition of a new event, and corresponding tests to ensure the functionality works as expected.
New Feature: Achievement Revocation
Documentation Update:
README.md
explaining how to revoke achievements using therevokeAchievement
method.AchievementRevoked
event inREADME.md
.Code Changes:
AchievementRevoked
event tosrc/Concerns/HasAchievements.php
.revokeAchievement
method insrc/Concerns/HasAchievements.php
, which detaches the achievement from the user and dispatches theAchievementRevoked
event.Event Addition:
AchievementRevoked
event class insrc/Events/AchievementRevoked.php
.Testing:
tests/Concerns/HasAchievementsTest.php
to cover scenarios such as revoking an achievement, ensuring the event is dispatched, and handling errors when revoking unearned achievements. [1] [2]Type of Change
Related Issues and Pull Requests
Testing
Please provide a passing test where possible. This package uses PestPHP
Checklist: