We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we ignore any fields in name questions, and instead just provide a single 'full name' field, like this:
This follows best practice in the GOV.UK Design System, but there may be occasions where a name needs to be broken down into multiple fields.
This is a good example of a more general design consideration a tool like this must deal with:
To what extent should we override the design of questions in the document form in favour of our preferred patterns? If we override a pattern, can and should we notify the user, and how?
To what extent should we override the design of questions in the document form in favour of our preferred patterns?
If we override a pattern, can and should we notify the user, and how?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently we ignore any fields in name questions, and instead just provide a single 'full name' field, like this:
This follows best practice in the GOV.UK Design System, but there may be occasions where a name needs to be broken down into multiple fields.
This is a good example of a more general design consideration a tool like this must deal with:
The text was updated successfully, but these errors were encountered: