Support for component field types

Created on 6 August 2024, about 2 months ago
Updated 8 August 2024, about 1 month ago

Problem/Motivation

Back in issue ✨ Add other field types Closed: works as designed there was a lot of work done getting a plugin system going. The component field functionality didn't make the cut for that release, so I thought I'd open a new issue to track it since I still need that functionality and it seems generally useful for a variety of plugins.

Proposed resolution

The attached patch follows the same approach as it did back in the old patch, but I updated it to work better with form improvements that have been made since that version of the module.

Remaining tasks

One known issue is that when you switch from the Default mapper plugin to a field specific one that supports component fields, you need to resave the configuration screen before those component fields will show. I imagine adding some sort of ajax callback on mapper switch could fix that issue.

✨ Feature request
Status

Needs review

Version

4.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States jacobbell84

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

Comments & Activities

Production build 0.71.5 2024