Support for the "has value" condition via Conditional fields plugins. The goal is to cover all core form field widgets. For this we have a handler plugin system in Conditional fields with one plugin for each field form widget to support.
(Summary edited by maintainers.)

Comments

OlgaRabodzei created an issue. See original summary.

OlgaRabodzei’s picture

OlgaRabodzei CreditAttribution: OlgaRabodzei at Adyax commented
Issue summary: View changes
OlgaRabodzei’s picture

OlgaRabodzei CreditAttribution: OlgaRabodzei at Adyax commented
Issue summary: View changes
OlgaRabodzei’s picture

OlgaRabodzei CreditAttribution: OlgaRabodzei at Adyax commented
Issue summary: View changes
OlgaRabodzei’s picture

OlgaRabodzei CreditAttribution: OlgaRabodzei at Adyax commented
Issue summary: View changes
colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
CreditAttribution: colan at Colan Schwartz Consulting commented
Title: Support value condition - widget » [META] Support value condition - widget
colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
CreditAttribution: colan at Colan Schwartz Consulting commented
Title: [META] Support value condition - widget » [META] Support all core widgets
colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
CreditAttribution: colan at Colan Schwartz Consulting commented
Assigned: OlgaRabodzei » Unassigned
dqd’s picture

dqd
(formerly "diqidoq")
CreditAttribution: dqd as a volunteer and at MAROQQO studios commented
Title: [META] Support all core widgets » Support for value input on all core field widgets
Version: 8.x-1.x-dev » 4.x-dev
Priority: Major » Normal
Status: Active » Closed (won't fix)

What widgets refers this issue to and would should they do? I assume we talk about field form widgets and the input of a certain value as condition ("has value" condition)? Change title accordingly.

Here a list of plugins and therefor core form field widgets already supported for "has value" input condition:

  • Core:
    • Checkbox
    • DateDefault
    • DateList
    • DefaultStateHandler
    • EmailDefault
    • EntityReference
    • EntityReferenceTags
    • LanguageSelect
    • LinkField
    • Number
    • OptionsButtons
    • Select
    • TextAreaFormated
    • TextDefault
  • Contrib:
    • LinkAddressfield
    • Shs

Apart from that: I think adding support for core field form widget "has value" input is like hunting the white rabbit. It is not only node but also user fields, media fields, and so on. And there will be surely more in the next year or some will be removed from core... and so on. I am not sure if this is a good idea to run this as META tagged for a final release. This will be an endless issue. For maintainability I would rather suggest to close this in favor of single issues to be created when a user realizes that his widget is not 100% supported yet and a lot users wishes to implement it. So the module can grow healthy without maintainer burn out.

We have far more to do yet to fix some major problems on the base of the project and should concentrate on that for a final Drupal 10/11 release.

dqd’s picture

dqd
(formerly "diqidoq")
CreditAttribution: dqd as a volunteer and at MAROQQO studios commented
Title: Support for value input on all core field widgets » Support for "has value" input on all core field widgets
Issue summary: View changes

Changed the issue summary accordingly for better understanding what this issue used to be about.

dqd’s picture

dqd
(formerly "diqidoq")
CreditAttribution: dqd as a volunteer and at MAROQQO studios commented
Issue summary: View changes