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
Writing this lib in CoffeeScript has provided a big productivity and robustness boost, but we could probably get those same benefits with ES6 now — along with broader approachability and appeal.
We might not be able to port the tests from CoffeeScript yet, assuming we still want to use Streamline (that provides an even bigger productivity and robustness boost when writing tests), until Streamline implements support for Babel too — which is on its roadmap.
Just found this lib as I started working with neo4j, and I heavily +1 for porting to ES6!
CoffeScript was nice as long as ES5 was around, but at latest with the release of node.js v4.0 you have a lot similarity.
For rewriting streamline stuff, I suggest using async / await, which is in Stage 2 and thus enabled by default in Babel (ref.)
+1 as well, not necessarily because it's ES6 but because it's no longer coffeescript and will open the door to more pull requests (especially from my end, eg for #164 :-)).
+1. CoffeeScript is a significant hurdle to get past for wanna-be contributors. The Neo4j driver landscape is full of abandoned and poorly-written code, but v2 of this repo seems very promising. CS is the only reservation I have when considering its use in production.
Writing this lib in CoffeeScript has provided a big productivity and robustness boost, but we could probably get those same benefits with ES6 now — along with broader approachability and appeal.
https://babeljs.io/
https://babeljs.io/docs/learn-es6/
We might not be able to port the tests from CoffeeScript yet, assuming we still want to use Streamline (that provides an even bigger productivity and robustness boost when writing tests), until Streamline implements support for Babel too — which is on its roadmap.
Sage/streamlinejs#254
The text was updated successfully, but these errors were encountered: