List field types: replace implementations of validateAllowedValue() with Typeddata validation

Created on 26 March 2014, about 11 years ago

Updated 13 March 2025, about 1 month ago

Followup from #2169983: Move type-specific logic from ListItemBase to the appropriate subclass → :

validateAllowedValue() validates that the input for the "allowed values" settings UI is valid for the List* field type (int, float, text...)
It would be best as a single generic implementation in ListItemBase, that validates the value against the TypedData definition of the 'value' property defined in propertyDefinitions(), which already specifies all the constraints we need and is able to check them.

Also this could help to decouple BooleanItem to Core

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

options.module

Created by

🇫🇷France yched

Live updates comments and jobs are added and updated live.

Entity Field API

Entity validation

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 1 month ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024