Rewrite Status

[tivac]

Let's have a single place to track the rewrite status!

(As best as I can figure it at least, some things are still just stored in @lhorie's head :smile:)

Alpha

• [x] Test runner
• [x] Bundling script
• [x] DOM diffing
• [x] Hyperscript API
• [x] Lifecycle methods
• [x] v0.2.x-style API
• [x] Rate-limit redraws when mounted
• [x] prevent redraws from event handlers
• [x] basic m.prop() support
• [x] Promise polyfill
• [x] v0.2.x :arrow_right: v1.x Migration Guide
• [x] shouldUpdate :arrow_right: onbeforeupdate (discussion)
• [x] Test DOM recycling w/ components
• [x] glue m.prop, Promise, m.request, and redraws together somehow
• [x] fix #1100
• [x] #1095 - Routing hook
• [x] Tests for contenteditable
• [x] #1132 - Public API for piecemeal consumption require("mithril/route")
• [ ] Tests for custom elements
• [ ] finish docs
• [ ] #1014 - Don't output booleans from hyperscript API

Beta

• [x] IE perf improvements from https://github.com/lhorie/mithril.js/pull/1016

NOTE: This isn't an issue for discussing API design/rewrite bugs/etc, those should happen in their own more focused issues.

[dead-claudia]

@tivac @lhorie I added a Rewrite milestone to help better categorize things, and I've added them to several existing issues. Welcome.

[lhorie]

Update: major breaking change: promises are now gone in favor of streams. See docs for m.prop for more details on how streams work

[nordfjord]

@lhorie would love to see more "Array" methods on the streams.

e.g. forEach, filter, reduce

let userStream = m.prop()
  .filter(user => user.isVisibleOnline)
  .forEach(user => {
    displayUserLoginPopup(user);
  });

subscribeToUserChannel(userStream);

[tinchoz49]

Yes i aggree with @nordfjord and maybe if the streams has an API compatible for example with the flyd streams we can extend the methods using their modules (filter, lift, flatmap...) without increase the size and the API stream functions in mithril.

BTW: great idea add the stream support. :+1: :rocket:

[darsain]

@lhorie if it's a breaking change already, why make it ambiguous by still calling it m.prop? Just name it m.stream :)

[dead-claudia]

@darsain It's still mostly the old m.prop. Just instead of incorporating itself with Promises, it's incorporating itself into the Streams world (which also helps observability).

[pietermartin]

Any more info regarding the status of the rewrite. We are planning on rewriting a large Angular 1 app and Mithril looks great but alas the status?

[lhorie]

@pietermartin it's currently at release candidate 2

[lhorie]

update: taking these out:

- [ ] #618 - ES6 classes as components
- [ ] `m.startComputation()` & `m.endComputation()`

[kylebakerio]

Migration guide link is dead. link to docs for m.prop discussing breaking change to streams is dead.

[tivac]

Closing this as rewrite status is being tracked by the milestone now.

[gyandeeps]

"IE perf improvements" was marked done but I don't see it in the code. Am I missing something or was it dropped from the plan?

[tivac]

@gyandeeps Hmm, might've gotten lost in a re-shuffle. Would you be willing to open a new PR? 😞

[gyandeeps]

@tivac I am loaded with work currently, i can when i get some time but meanwhile if somebody else wnat to do it feel free.

More details:

Here is the previous PR: https://github.com/lhorie/mithril.js/pull/1016 Issue comment: https://github.com/lhorie/mithril.js/issues/199#issuecomment-210110023

This should give enough information.

Theme: Add the element to its parent before you add its children to it. this has perf imrovments on IE engines.

[gyandeeps]

@tivac Spent some time today to get this work: https://github.com/lhorie/mithril.js/pull/1598

[lhorie]

added some love for @gyandeeps : http://mithril.js.org/credits.html