You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than adding new fields for each of these (and more in the future), which serve to clutter the form builder, I propose we build a single "Custom Field" field that allows you to add support for any Craft field, or plugin-provided Craft field.
However, we'll still need to opt-in support for each field, as we need to define a few things for a Formie-enabled field:
Front-end template
Field settings (Formkit-compatible)
Email Notification template
Integration, export and string representations
But the benefits of having a field geared towards Craft custom fields are:
Submission editing in the control panel UI is sorted
Field normalization is provided by field implementation
Less fields to manage in the form builder
Developers can provide their own support for their Craft field in Formie
The text was updated successfully, but these errors were encountered:
In reference to a few new field suggestions:
Rather than adding new fields for each of these (and more in the future), which serve to clutter the form builder, I propose we build a single "Custom Field" field that allows you to add support for any Craft field, or plugin-provided Craft field.
However, we'll still need to opt-in support for each field, as we need to define a few things for a Formie-enabled field:
But the benefits of having a field geared towards Craft custom fields are:
The text was updated successfully, but these errors were encountered: