mithril-vndb/docs/nav-methods.md at 696b5cbfe34f2ff51e626b8bd5175d4e3d27a7ef

Remove m.prop + m.withAttr (#2317 )

* Remove `m.prop` + `m.withAttr`

- For many uses, `m.withAttr` is *more* verbose than just directly using
  an event handler
- If you're using it with a bound callback, you're literally wasting a
  single character in the human readable version (and you're *saving*
  them in the minified output).
- It sometimes obscures your intent, if overused.
- Functions are easier to compress than `m.withAttr`, resulting in
  slightly smaller bundles.
- `m.withAttr` is overused anyways.
- `m.prop` is basically useless without `m.withAttr`, and the API
  doesn't have the same benefits it had with 0.2.x.

* Update changelog

2018-11-30 20:41:24 -05:00

484 B

Raw Blame History

Core
- m
- m.render
- m.mount
- m.route
- m.request
- m.jsonp
- m.parseQueryString
- m.buildQueryString
- m.trust
- m.fragment
- m.redraw
- m.version
- Promise
Optional
- Stream
Tooling
- Ospec

484 B Raw Blame History

484 B

Raw Blame History