Added mention of HTML5 fields in the docs #326
Conversation
|
Looks like you used a different email than the one associated with your GitHub account. If you want to change that, you can use |
|
Thanks for that! |
| ------------ | ||
|
|
||
| In addition to basic HTML fields, WTForms also supplies fields for the HTML5 | ||
| standard. These fields can be accessed under the `wtforms.fields.html5` namespace. |
There was a problem hiding this comment.
Decorate `wtforms.fields.html5` as :mod:`wtforms.fields.html5` .
| In addition to basic HTML fields, WTForms also supplies fields for the HTML5 | ||
| standard. These fields can be accessed under the `wtforms.fields.html5` namespace. | ||
| In reality, these fields are just convenience fields that extend basic fields | ||
| and implement HTML5 specific widgets. These widgets are located in the `wtforms.widgets.html5` |
| namespace and can be overridden or modified just like any other widget. | ||
|
|
||
| .. autoclass:: SearchField(default field arguments) | ||
| Represents an `<input type="search">` field |
There was a problem hiding this comment.
Use `` instead of ` to decorate all HTML code.
| Represents an `<input type="datetime-local">` field | ||
|
|
||
| .. autoclass:: IntegerField(default field arguments) | ||
| Represents an `<input type="number">` field with the `step="1"` attribute |
There was a problem hiding this comment.
Also use `` instead of ` here and below for the HTML step attribute.
|
Thanks for the suggestions. I'll clean these up tomorrow and push them up |
|
Cool. I'm still learning how Sphinx works. Thanks for the heads up! |
|
I'm having some issues with building. Sphinx doesn't seem to like the fact that these classes are in the |
|
@davidism, what are the changes that still need to be done to get this sorted? This seems like something that really should be in the docs so I'm happy to make the changes myself. |
|
Does it build? Looks fine otherwise. |
|
It didn't build, it needed a few changes so I made those and merged it in a separate PR #409 but it should also realise this has been merged too. |
Per request of #275, adding the HTML5 fields to the Fields documentation