allow experimental object rest/spread

[helloyou2012]

bug fix for: max-mapper/standard-format#145

[millermedeiros]

can you add a test to avoid regressions? https://github.com/millermedeiros/esformatter-semicolon-first/tree/master/test/compare - just need to include an example on the input and output files and run npm test to check it:

cd esformatter-semicolon-first
npm i
npm test

the best fix would be to replace espree with esformatter-parser, but this also works.

[helloyou2012]

Ok, I will add test case.

[millermedeiros]

uhm.. weird that this behavior changed. I would not expect the code to be formatted this way.

[helloyou2012]

Before that, this behavior have changed. Maybe espree have changed. I'm checking.

[helloyou2012]

Source :

var x = 2
[1,2,3].map(function() {})

esformatter-semicolon-first plugin run stringBefore :

var x = 2
;[1,2,3].map(function() {})

After VariableDeclaration transform to :

var x = 2;
[1, 2, 3].map(function() {})

esformatter-semicolon-first plugin run tokenAfter :

var x = 2;[1, 2, 3].map(function() {})

PS: tokenAfter should not be necessary.

[millermedeiros]

uhm, I'll check this later. seems really weird. I'm sure behavior was fine previously. maybe esformatter is doing more stuff than before... or maybe I should just add the ; on stringAfter instead.

[millermedeiros]

@helloyou2012 I ended up updating the parser and using your test cases (did some aggressive rebase but kept you as the commit author)

thanks a lot for bringing this into my attention. I'm not using this plugin on my own projects (I like semicolons) so I would not notice it was broken. Cheers!

[millermedeiros]

just released v1.2.0 with the fix!