You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the playground uses Klipse which uses CodeMirror. It works fine, but an editor like Monaco could fairly easily be configured to provide completion and online documentation.
The text was updated successfully, but these errors were encountered:
When working on a new playground, I think it would be awesome to add a small performance test loop to it. It doesn't need to be as advanced as jsperf, but a simple test so we can see how good a implementation of specific lenses perform.
The parsing of code in the playground can take some time, when a data object becomes larger (L.collectAs(myFn, [L.elems, 'sub', L.elems, 'path', L.choose....], largeDataObject). Being able to run the final L statement in a loop, would give some helpful feedback.
Hmm... Interesting idea! Note that all the current interactive pages (playground, exercises, and readme) use the development (rather than production) browser build of the library, which includes extra run-time checking code and runs significantly slower than the production build. So, it might be useful to have a separate benchmarking page with the production build.
Currently the playground uses Klipse which uses CodeMirror. It works fine, but an editor like Monaco could fairly easily be configured to provide completion and online documentation.
The text was updated successfully, but these errors were encountered: