Problem/Motivation

While testing Display Builder entity overrides, I was confused because only my first block appeared.

It was due to the cardinality of the ui_patterns_field used to store DB override set to 1 by default.

I suggest to have unlimited by default. Or if cardinality of one is intentional, explicit it in the code.

Issue fork ui_patterns-3558748

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

grimreaper created an issue. See original summary.

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Assigned: grimreaper » just_like_good_vibes
Status: Active » Needs review

grimreaper opened merge request !466

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Assigned: just_like_good_vibes » grimreaper
Status: Needs review » Needs work

Fixing CI before review.

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Assigned: grimreaper » just_like_good_vibes
Status: Needs work » Needs review

just_like_good_vibes made their first commit to this issue’s fork.

just_like_good_vibes’s picture

just_like_good_vibes
Location PARIS
commented
Assigned: just_like_good_vibes » christian.wiedemann

there is a debate, about having 1 or unlimited by default.
it's a nice to have for display builder, when we invite the user the add a field for display override.

but at the same time, it is not suited for other use cases.

let's take time and wait for other inputs

just_like_good_vibes’s picture

just_like_good_vibes
Location PARIS
commented
Assigned: christian.wiedemann » pdureau
Status: Needs review » Postponed

we may do something else in display builder and that would close this issue.
Pierre will add the link to the display builder issue.

pdureau’s picture

pdureau commented
Assigned: pdureau » Unassigned
Status: Postponed » Closed (works as designed)

We have partially automated the creation of this field in Display Builder. Let's hope it is enough.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.