[8.x] Allow components to use custom attribute bag #36186
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 PR allows a developer to provide a custom
ComponentAttributeBag
instance for their view's components.I really liked the idea on PR #36148 , but I totally get that merging it would expand the maintenance work for a feature not all users would use.
By allowing the developer to override the
ComponentAttributeBag
instantiation, a third-party package could provide the features from PR #36148 .Also it is similar to how an Eloquent Model allows a custom Collection or Query Builder instantiation.