List support for views

Created on 14 November 2023, about 1 year ago
Updated 15 November 2023, about 1 year ago

Problem/Motivation

When a list subtype is created, it is created as a simple text one, and the "list" behavior is added only as a widget.
The problem is that using that field in a view looses the characteristic of a list, it is just a text field, so for example the user cannot filter by allowed values.
This does not happen with a standard Text/List field.

Steps to reproduce

Proposed resolution

Is it possible to define a field as a list so that this characteristic is preserved when used in a view?

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Closed: works as designed

Version

1.0

Component

Code

Created by

🇮🇹Italy giuse69

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @giuse69
  • Status changed to Closed: works as designed about 1 year ago
  • 🇫🇷France lazzyvn paris

    Please read again module description

    Please note: all custom fields are not entity fields, so you cannot benefit from field widget, field renderer, or the entity formatter. It's just for the data.

Production build 0.71.5 2024