Closed jakecraige closed 7 years ago
Basically, the issue is that JSHint isn't updated to handle all of the various ES6 options.
In ember-cli we are hinting against the actual source in app (which is not processed through esnext filter yet).
I'm thinking we need to allow some plugins to be pre-JSHint (sweet.js and esnext) and others to be post-JSHint (like coffeescript).
Alternatively, we could look into options other than JSHint that may be more aware of ES6 semantics.
It seems jshint isn't respecting the template strings syntax
error:
offending code:
I'm not sure if this is just a jshint setting i need to set or if this addon can somehow fix this but I wanted to bring it up.