-
-
Notifications
You must be signed in to change notification settings - Fork 309
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
Rename Form to FlaskForm #249
Comments
I agree. |
show deprecation warning when using Form closes #249
show deprecation warning when using Form closes #249
show deprecation warning when using Form closes #249
Could you release and update the version in pypi so that users using pip can follow the new documentation? |
You're looking at the dev docs. Use the menu in the bottom right corner to select the stable docs. I do plan on making a release "soon", but want to get a few more changes in. |
Hi @davidism, how much time is needed to update to 0.14 on PIP ? I saw that you have a commit changing to last version, but it isn't reflected yet. |
That's the development version, there's no changes yet. I literally just released 0.13 this morning. |
A common issue users have is that they imported
wtforms.Form
when they meantflask_wtf.Form
, or vice versa, or they imported both and one is masking the other. We should renameflask_wtf.Form
toflask_wtf.FlaskForm
, and treatForm
as a deprecated alias that raises a warning when it is used.This also makes it easier to subclass both types of form in one file. For example when you want to create forms for
FormField
and only have CSRF handling in the main form. Right now you need to import one of the forms with an alias.The text was updated successfully, but these errors were encountered: