Maybe we would be better off using ES5 / ES next or something since ES2016 ended up having 2 new features in comparison to ES2015:
And ES2017 will probably have just as little new stuff.
ES5/ES6/ES7 version names are used mainly in the code examples and example projects. Maybe we should only divide these into ES5/ES next or even lose the ES5 alltogether and just write everything using newest shiniest node features. What do you think?
Maybe we should only divide these into ES5/ES next
I like that idea.
just write everything using newest shiniest node features
That's gonna make the examples simpler 👍 . I mean assuming that everybody is using the latest released version of node. But that's more debatable.
You could write in the style of the latest node LTS version– that gives a natural progression people are already familiar with.
Personally I wouldn't mind had objection.js docs only included ES next examples. But a small description of how to downgrade some ES next sugar could be useful as a minor separate segment perhaps.
@devinivy That would mean constant updating and everyone hates writing docs :trollface:
@fl0w I like that idea!
http://knexjs.org/ has a cool feature at the top right hand side where you can pick an SQL dialect. The Objection.js documentation would be much easier to navigate if visitors could switch between different ES versions for the examples!
ES5 support is now removed in the master branch and will be released with 0.8.0. ES5 examples have been removed, node 4.0.0 examples are the default (the lowest supported node version) and then there are ESNext examples. Node 4.0.0 basically means ES2015 without some features like destructuring and rest parameters.
Most helpful comment
Maybe we would be better off using ES5 / ES next or something since ES2016 ended up having 2 new features in comparison to ES2015:
And ES2017 will probably have just as little new stuff.
ES5/ES6/ES7 version names are used mainly in the code examples and example projects. Maybe we should only divide these into ES5/ES next or even lose the ES5 alltogether and just write everything using newest shiniest node features. What do you think?