refactor: cleanup files - #12
Merged
victormgomes merged 1 commit intoJul 29, 2026
Merged
Conversation
victormgomes
deleted the
refactor/replace-comments-with-self-documenting-code
branch
July 29, 2026 08:55
|
🎉 This PR is included in version 2.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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
Refactor the codebase to replace explanatory comments with self-documenting code
through better naming, extracted methods, and type-safe constructs. Also translates
all Portuguese log messages and descriptions to English.
Type of change
to not work as expected)
Checklist
composer run format).README.md).works.
composer run test).composer run test-coverage).run
composer run insights).Note: The Security parameter in the #[AsyncApi] attribute kept its name and is just a PHPDoc addition, but renaming $action from string to the new Action enum could break users who pass a raw string 'send' instead of Action::Send. Hence the breaking change category. If you don't consider that breaking, move it to a regular refactor.