Apologies for not having full ES6 support yet, we actually do support a number of ES6 features (like destructuring). The rest are mainly due to my laziness (lack of time). The code undergoes a transformation where I need to know about all the local variables in each cell for the time traveling feature, and certain things like import statements add new local variables references that I just haven't had the time to support so they're not whitelisted.
The feature in question is the following. We support hosting, so you could have two cells like this:
[Cell 1]
f()
[Cell 2]
function f()
{
return 5;
}
Normally "dirtying" is simple, if a cell from the past has changes, then the future changes. However with hoisting, sometimes the future can change the past. You'll see that in Tonic if you were to change the 5 to a 7, Cell 1 would appropriately dim letting you know the machine will go back to that point to rerun.
ok now that ive used it theres one thing i dont like:
* im changing code in a block but every time i eval it the 3 code blocks above re-expand the results i just hid... because the last one was `_ = require('lodash')` it prints like 70 lines of func defs :/
minor gripes:
* console.log(1,2) produces two lines of output, the browser version produces "1 2" (and then wraps every 3 lines, kind of inconvient when you log (i, array[i]))
* ctrl - y redo doesnt work (ctrl z does tho)
* the dom jitter from the results div disappearing, pause, appending "loading", then appending a large div, feels off. possibly lock the height, then replace contents w/ "loading", then transition to the new results size, if you can calculate that is better. really good tool tho gj.
really minor issues! im not logged in, idk if that matters
I am actually working on this exact issue right now :) Hopefully will be fixed very soon.
Yeah the console.log thing is for when you have two objects, you want them on two lines. However, we could get smarter and collapse lines (that were together) if they have no fancy object viewers.
And yes -- I don't know why we chose three, we'll probably expand that.
Sorry about redo, it should work, we'll look into it.
