Support for "has value" input on all core field widgets

Created on 7 April 2017, about 7 years ago
Updated 7 March 2024, 4 months ago

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.)

πŸ“Œ Task
Status

Closed: won't fix

Version

4.0

Component

Code

Created by

πŸ‡ΊπŸ‡¦Ukraine OlgaRabodzei

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.

  • πŸ‡©πŸ‡ͺGermany diqidoq Berlin | Hamburg | New York | London | Paris

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

    Here the 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.

  • πŸ‡©πŸ‡ͺGermany diqidoq Berlin | Hamburg | New York | London | Paris

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

  • πŸ‡©πŸ‡ͺGermany diqidoq Berlin | Hamburg | New York | London | Paris
Production build 0.69.0 2024