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? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Currently we always generate day, month and year for a date input; the GDS fixtures have examples for day + month and month + year.
The text was updated successfully, but these errors were encountered:
@gunndabad FYI our implementation based on yours already has the month and year version, so getting this in the base library would be great.
Sorry, something went wrong.
@sussexrick do you support binding to a single model property in your implementation or do you have a property per field?
We have a single property and just assume the first of the month. That allows us to switch the day field on and off in our UI with no code changes.
No branches or pull requests
Currently we always generate day, month and year for a date input; the GDS fixtures have examples for day + month and month + year.
The text was updated successfully, but these errors were encountered: