Mainly to enable the rest/spread operator (...variable).
Other new features include asynchronous iteration,
Promise.prototype.finally and additions to RegExp (look behind, named
capture groups, s flag)
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
We use both, 'no-extra-parens' and 'no-mixed-operators' rules and
those can conflict. Thus follow eslints recommendation[0] and allow
parenthesis in nestedBinaryExpressions to avoid the linter
complaining either way. Do this also fo enforceForArrowConditionals
as there I saw the issue already in practice for me.
[0]: https://eslint.org/docs/rules/no-mixed-operators#rule-details
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
In generally we follow it but we want also to allow statements like:
let foo = bar
? 'baz'
: 'foz'
;
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Moving the message and the info if something is auto-fixable to a
single line, saving ~ 2/3rd of output lines.
The auto-fixable got replaced with a (*) marker, it's not ideal but
IMO OK; explain what it means in the summaries "X issues marked with
(*) could be auto-fixed"
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
we use this many times, and it really should not be confusing,
also it is much shorter than: 'Boolean(foo)',
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
This is a bit strange behaviour, especially if there's nothing to
lint and one gets just a spewed out nodejs backtracke.. It's not hard
to just to `eslint *.js` or the like..
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
who the heck makes the following syntax the default:
> foo.
> bar().
> baz();
So let's enforce the right thing™ and enforce the dot sticking to the
property, not the object, i.e.:
> foo
> .bar().
> .baz();
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
I mean some seem to like python style throwing up in ones face on
every occasion.. I don't though..
nodes drops the original argv0 in favor of process.execPath and the
path to the JavaScript file being executed, so we need more than two
args to be OK.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
