Trait for builders using components #1440
Merged
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.
This pull request refactors the handling of components in several builder classes by introducing a reusable trait,
ComponentsTrait. The trait consolidates the logic for managing components, reducing code duplication and improving maintainability. The change affects multiple builder classes, which now use the trait instead of their own implementations ofsetComponentsandaddComponents.Trait introduction and code deduplication
ComponentsTraitinsrc/Discord/Builders/ComponentsTrait.php, encapsulating shared logic for setting and adding components, and requiring anaddComponentmethod in the using class.ActionRow,Container,Section,MessageBuilder, andModalBuilderclasses to useComponentsTrait, removing their individual implementations ofsetComponentsandaddComponents. [1] [2] [3] [4] [5] [6] [7] [8]Removal of redundant methods
setComponentsandaddComponentsmethods fromActionRow,Container,Section,MessageBuilder, andModalBuilder, as their functionality is replaced by the trait. [1] [2] [3] [4] [5]These changes make the codebase cleaner and more maintainable by centralizing common component logic.