Modified html_params to treat aria attributes the same as data attributes #389
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
azmeuk
added a commit
to azmeuk/wtforms
that referenced
this pull request
Apr 18, 2020
azmeuk
added a commit
to azmeuk/wtforms
that referenced
this pull request
Apr 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing #239, when specifying field attributes in a template if the attribute begins with
aria_, then the generated attribute shall begin witharia-, just like howdataattributes are handled.For example
{{ form.username(aria_describedby='usernameHelp') }}will now make
I also corrected the documentation for
html_params, clarifying how when usingdata_oraria_attributes every underscore gets replaced with a hyphen - not just the first one.