can do the same for trailingFunctionCommas, dono if you want that in a separate one

we should deprecate classConstructorCall too

Current coverage is 96.91% (diff: 100%)

Merging #98 into master will decrease coverage by <.01%

@@             master        #98   diff @@
==========================================
  Files            19         19          
  Lines          2922       2919     -3   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
- Hits           2832       2829     -3   
  Misses           90         90          
  Partials          0          0          

Powered by Codecov. Last update b649671...1349baa

I also started restructuring and renaming the test dirs
at first i wanted to do something like

--es
  -- 2015
  -- 2016

but babel-helper-fixtures is limited to how deep one can nest dirs, so I did this now:

-- es2015
-- es2016

Gonna do all in this PR.

I'm not sure how to proceed with classConstructorCall probably we can just remove it with the next major. Should we log a warning if it is used already?

Yeah we would remove it in the next major - just not sure given we would need to update babel too. You can just leave it for now.

I updated the docs a while ago (http://babeljs.io/docs/plugins/transform-class-constructor-call/) but not sure who looks at it