Skip to content
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

0.11 #64

Closed
16 tasks done
insin opened this issue Mar 5, 2015 · 2 comments
Closed
16 tasks done

0.11 #64

insin opened this issue Mar 5, 2015 · 2 comments

Comments

@insin
Copy link
Owner

insin commented Mar 5, 2015

  • Remove render(), asDiv(), asTable() and asUl().
  • Deprecate formsetFactory()
    • Rename BaseFormSet to FormSet
    • FormSet constructor can be used directly or .extend()ed to set defaults which used to be passed to formsetFactory().
  • Modularise - break everything into individual modules
    • Default require('newforms') will still give you a grab-bag of everything
    • Publish to npm as flattened modules - people who want to save on dependency file size when bundling can directly import only what they need - in particular, you should never need to bundle FormSets if you're not using them.
  • Populate form.files and cleanedData with File objects on the client (FileField never updates  #61)
    • API docs
  • MultipleFileField
  • Add a new core Field property: field.widgetAttrs (Add support for some HTML Input attributes  #62, Allow to set focus on a field #63)
    • Rename Field.prototype.widgetAttrs to getWidgetAttrs
    • Return field.widgetAttrs by default
    • Make sure overrides of getWidgetAttrs are calling super() properly
  • Don't restrict widget attrs defaulted by numeric fields based on widget type (IntegerField only passes value limits to NumberWidget #59)
  • Start UPGRADE_GUIDE.md with features removed in this release and deprecated for removal in the next release.
@marr
Copy link

marr commented Mar 5, 2015

Looks like #61 landed, which can close "Populate form.files and cleanedData with File objects on the client". Does this mean that .11 is ready to go?

I am looking forward to the widgetAttrs feature. I believe that will let me change the input type? Ie, I'd like to use type="tel" to get the keypad on mobile web for numeric inputs.

Cheers,
Dave

@insin
Copy link
Owner Author

insin commented Mar 6, 2015

0.11 is almost ready. just want to play with the client-side File object change a bit first.

widgetAttrs is at the bottom of the stack in terms of precedence (widget.attrs < render()-generated attrs < attrs passed to render() via BoundField) so it won't let you override type.

TextInput treats the type attr specially to allow you to override the rendered type when creating an instance ( TextInput({attrs: {type: 'tel'}}) ), or you could extend it to create your own widget constructor ( var TelInput = TextInput.extend({inputType: 'tel'}) )

insin added a commit that referenced this issue Mar 6, 2015
@insin insin closed this as completed Mar 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants