26b8d994ce
* 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
26 lines
780 B
JavaScript
26 lines
780 B
JavaScript
"use strict"
|
|
|
|
var hyperscript = require("./hyperscript")
|
|
var m = function m() { return hyperscript.apply(this, arguments) }
|
|
m.m = hyperscript
|
|
m.trust = hyperscript.trust
|
|
m.fragment = hyperscript.fragment
|
|
|
|
var requestService = require("./request")
|
|
var redrawService = require("./redraw")
|
|
|
|
requestService.setCompletionCallback(redrawService.redraw)
|
|
|
|
m.mount = require("./mount")
|
|
m.route = require("./route")
|
|
m.render = require("./render").render
|
|
m.redraw = redrawService.redraw
|
|
m.request = requestService.request
|
|
m.jsonp = requestService.jsonp
|
|
m.parseQueryString = require("./querystring/parse")
|
|
m.buildQueryString = require("./querystring/build")
|
|
m.version = "bleeding-edge"
|
|
m.vnode = require("./render/vnode")
|
|
m.PromisePolyfill = require("./promise/polyfill")
|
|
|
|
module.exports = m
|