Problem/Motivation

A limitation of the current implementation is that it relies on form-level validation and so applies only in certain conditions. While issues like #2598864: Validation for overview menu form and #2598866: Validation for node form attempt to mitigate this limitation by adding new form validation, this approach still misses any non-form menu item manipulation or creation, such as via REST.

Proposed resolution

Use the entity validation API, adding a validator to the entity type.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

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:

Comments

nedjo created an issue. See original summary.

cyberschorsch’s picture

Version: 8.x-1.x-dev » 2.x-dev

cyberschorsch’s picture

Status: Active » Needs review

  • Cyberschorsch committed d8b05cd on 2.x
    Issue #3114458 by Cyberschorsch: Use entity validation API rather than...
cyberschorsch’s picture

Status: Needs review » Fixed

Fixed in new release 2.x

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.