allow for the field layout to be passed to the registerCardAttributes event #17920
Conversation
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
brandonkelly
deleted the
feature/registerCardAttributes-and-field-layout
branch
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
The
Element::EVENT_REGISTER_CARD_ATTRIBUTESevent allows you to adjust what card attributes are available in the card view designer. However, if you want to, e.g. add a new attribute, there’s currently no way to limit that addition to e.g. a specific entry type or to a field layout that contains a specific field.This PR adds the ability to pass the
FieldLayoutto theRegisterElementCardAttributesEvent, giving you greater control over when card attributes should be adjusted.Related issues
n/a; from a conversation with @tommysvr