Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use webform element's name attribute (if set) as field key/name #1410

Open
3 of 4 tasks
bgilhome-now opened this issue Dec 12, 2024 · 0 comments
Open
3 of 4 tasks

Use webform element's name attribute (if set) as field key/name #1410

bgilhome-now opened this issue Dec 12, 2024 · 0 comments
Assignees
Labels
Proposal - Draft New feature proposal

Comments

@bgilhome-now
Copy link
Contributor

Describe the feature

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Proposal - Draft New feature proposal
Projects
None yet
Development

No branches or pull requests

2 participants