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
Currently in the webform mapping, the webform element's machine name (e.g. my_field) is used as the HTML input's name attribute. It would be good if the mapping could support using the name attribute set in the webform element's config if it's filled (e.g. myCustomFieldName).
Motivation
This is handy for webforms which submit to an API endpoint or other external service, which might use parameters with camel case or other cases (not snake case like machine names).
Proposal
Update the webform mapping to support using the name attribute if set in webform element config.
Benefits
Easier integration for forms with handlers using external APIs or other services.
Drawbacks
Will have to check if any existing code e.g. for regular handlers expects names to be snake case.
Adoption strategy
Add to documentation.
Additional information
Would you be willing to help implement this feature?
Could this feature be created outside of Ripple-framework as a layer?
Final checks
I have read the contribution guide for information on submitting a feature request.
I have checked the discussions and issues for duplicate feature requests.
The text was updated successfully, but these errors were encountered:
Describe the feature
Currently in the webform mapping, the webform element's machine name (e.g.
my_field
) is used as the HTML input'sname
attribute. It would be good if the mapping could support using the name attribute set in the webform element's config if it's filled (e.g.myCustomFieldName
).Motivation
This is handy for webforms which submit to an API endpoint or other external service, which might use parameters with camel case or other cases (not snake case like machine names).
Proposal
Update the webform mapping to support using the
name
attribute if set in webform element config.Benefits
Easier integration for forms with handlers using external APIs or other services.
Drawbacks
Will have to check if any existing code e.g. for regular handlers expects names to be snake case.
Adoption strategy
Add to documentation.
Additional information
Final checks
The text was updated successfully, but these errors were encountered: