Discuss adding a 'status' field type that could be used in place of 'boolean'

Created on 15 January 2018, almost 7 years ago
Updated 12 July 2023, over 1 year ago

Problem/Motivation

BooleanItem is used for User->status, Node->published, etc.

However when creating a sample version, it is usually expected that the user not be blocked, that the node be published, etc.

Yet other Boolean fields should still be truly random in their samples.

Proposed resolution

Create a dedicated field type for 'status'.

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Needs work

Version

11.0 🔥

Component
Field 

Last updated about 14 hours ago

Created by

🇺🇸United States tim.plunkett Philadelphia

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

Comments & Activities

Not all content is available!

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

  • 🇸🇰Slovakia petiar

    Within the Split “blocked” status into “pending” and “locked-out” Active it is requested to split the Blocked user status into the Locked out and Pending, so we know exactly why is the user blocked. However, for this purpose the status field type plugin as proposed here would not be sufficient because of it's boolean base. Is it alright if I implement new field type plugin (user_status, as suggested above in this thread) for the User entity or was there an intention to create a status field type plugin which would be applicable for any entity type?

Production build 0.71.5 2024