Add a setting to only compare within same bundle [#3544902]

Problem/Motivation

Sometimes you only want to ensure that the same title doesn't exist in the same bundle.

So I'd vote to add a setting to only check for uniqueness within the same bundle. Disabled by default.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork unique_entity_title-3544902

Show commands

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

Add & fetch this issue fork’s repository

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

Add & fetch this issue fork’s repository

3544902-add-a-setting changes, plain diff MR !7
Check out this branch for the first time

Check out existing branch, if you already have it locally

About issue forks

Comments

Comment #1

4 September 2025 at 14:45

anybody created an issue. See original summary.

Comment #2

27 September 2025 at 10:57

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

Comment #3

miroslavstankov commented 27 September 2025 at 10:57

Assigned:

Unassigned

» miroslavstankov

I would like to work on this issue

Comment #4

27 September 2025 at 13:40

miroslavstankov opened merge request !7

Comment #5

miroslavstankov commented 27 September 2025 at 13:43

Assigned:	miroslavstankov	» Unassigned
Status:	Active	» Needs review

This functionality—checking uniqueness only within the same bundle— as I can see is already implemented in the current codebase. I tested it with content types and taxonomy terms as follows:

- Tried adding the same title twice in the Article content type, and it correctly threw an error for duplicate titles.

- Then added the same title in a different content type (Basic page), and it allowed it, since uniqueness is scoped per bundle.

- Performed the same checks for taxonomy terms, with the expected behavior.

Additionally, I added a functional test to cover this scenario for extra assurance.

One more note: I replaced the deprecated @Constraint annotation with the newer PHP attribute syntax for validation constraints:

#[\Drupal\Core\Validation\Attribute\Constraint(
id: 'UniqueEntityTitle',
label: new TranslatableMarkup('Unique Entity Title', [], ['context' => 'Validation']),
type: ['string']
)]

Overall, no code changes are necessary to support the requested feature, as it’s already working as intended. Happy to discuss further if needed!