Fix description of namePrefix for date input#1570
Conversation
|
@colinrotherham @anandamaryon1 I've updated this description again, whaddya think? |
sarawilcox
left a comment
There was a problem hiding this comment.
Hi @colinrotherham , is there a typo here? "This is used to in the name attribute to group ..."
|
@sarawilcox Yeah there is, do you mind catching up with the review thread? |
|
I'm afraid I'm not understanding this very well, @colinrotherham . Maybe we can discuss with @anandamaryon1 at PR review meeting tomorrow. |
|
|
@sarawilcox I’ve fixed the typo 🤦, thanks. The short story is that in #994 we (well I) updated the date input component so that the name attributes use the format |
|
@anandamaryon1 @colinrotherham could you check this correction to the I can stick an issue on the backlog for a future debate about whether to rename/alias it from I don’t think this needs a changelog entry as it’s purely a documentation wording change, but happy to add one if you think otherwise? |
Co-authored-by: Colin Rotherham <work@colinr.com>
|
|
@colinrotherham created the issue at #1674. Ok to approve this now? |
The description of how the namePrefix is out of date, as in #994 we updated it to use square brackets instead of hyphens, for easier use with Express.js based servers (eg the NHS Prototype kit).



The description of how the
namePrefixis out of date, as in #994 we updated it to use square brackets instead of hyphens, for easier use with Express.js based servers (eg the NHS Prototype kit).