Ability to control the id and name attributes of the Date input items
See original GitHub issueCurrently the id
and name
are auto generated in the macro:
"id": params.id + "-" + item.name,
"name": params.name + "-" + item.name
I need more control over these. For example, let say I am capturing a DoB of a person:
<input type="number" name="person[dob].day" />
<input type="number" name="person[dob].month" />
<input type="number" name="person[dob].year" />
Would it be possible to include this capability?
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
<input type="date"> - HTML: HyperText Markup Language
The step attribute is a number that specifies the granularity that the value must adhere to, or the special value any , which...
Read more >Forms in HTML documents - W3C
A control's "control name" is given by its name attribute. The scope of the name attribute for a control within a FORM element...
Read more >Difference between id and name attributes in HTML
The name attribute is used when sending data in a form submission. Different controls respond differently. For example, you may have several ...
Read more >Product data specification - Google Merchant Center Help
Click the name of an attribute to view full details, including more ... need to let Google know about all the updates to...
Read more >HTML Id Attributes - GeeksforGeeks
Use of ID attributes in JavaScript: In JavaScript, the id attribute is used to manipulate the text, if you want to make changes...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@davidjamesstone just to let you know that we’ve now merged #984 which addresses #909 by renaming the
name
argument tonamePrefix
– it’ll be part of the next release of Frontend, which we expect to be v2.0.Thanks again for raising this and helping to improve Frontend! 👍
Thanks, I will keep an eye out for a documentation PR 👍 🎉
I’m going to split this into two issues so that we can track each one separately:
I’ve tried my best to summarise each issue, but please do feel free to add anything I might have missed.
I think that covers everything discussed in this issue, so I’m going to close this now. Please do re-open it or file another issue if you need to.