-
Notifications
You must be signed in to change notification settings - Fork 332
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
Confused by the documentation for radios 'conditional' #1903
Comments
@joelanman Can you provide a link to that in the docs, as that looks like it needs correcting? It should read:
(which I can see on https://design-system.service.gov.uk/components/checkboxes/) Good point about being able to provide a |
It was radios I was looking at: https://design-system.service.gov.uk/components/radios/ I would say even |
For now we've agreed just to remove the |
The documentation around this is still a bit off as it still suggests setting Documentation reference: https://design-system.service.gov.uk/components/radios/ |
The macro options for radios and checkboxes still display the |
just come across this again in my work - |
thanks! |
I was trying to use the conditional option on radios.
I saw that the example used
I didn't need html, just a sentence so I thought I could use
text
instead ofhtml
as you can in other places in Frontend. However, I tried it and it didn't work - there's no text option here.When I re-read the docs, I misread and thought the 'conditional' option, being a string, could just accept text.
However, I misread it, that doesn't work - the docs actually say:
But I don't think this is correct? In the examples,
conditional
is not a string, it's an object with only one property -html
I wonder if this might be better as two options:
conditionalHTML
andconditionalText
This would avoid another object, and be more consistent with the use of HTML and text elsewhere?
The text was updated successfully, but these errors were encountered: