* Change RenderField to use variadic parameter, so it can be called from...
... a template using only one parameter
- Allows manual field error setting to BaseForm (for exemple, to show API errors)
- Fields retain the entered value even on error
Fields retain the entered value even on error
I am not sure that this is the right thing, because that value does not pass validation. Can you please check what Ruby/Python libraries do in this case?
Both the first and third changes are for the retaining of the value between posts, like when there is an "Age" integer field, if the user entered "abc", the value would be cleared on post. This change makes the field stay "abc" after the post, which I think is less confusing.
I don't have experience in Rails, but in the PHP Yii framework, which is based on Rails, it works this way.
I think it is strange that some fields (text fields) retain invalid fields, and some (integer) don't, it is not common in sites I use frequently.