Julian Rosse
Julian Rosse
See #27 Should be able to provide Coffeescript-specific overrides for `eslint-plugin-vue` rules that don't work with Coffeescript out-of-the-box And could probably expose eg `plugin:coffee/vue-essential` configs similar to what we're doing...
Eg this: ``` throw new Error "DOOM was called with a null element" unless elm? for elm in elms ``` is definitely meant to be this: ``` (throw new Error...
I guess not just `do (x) ->` has special meaning but also `do name = (x) ->` So `no-shadow`/`no-unused-vars`' understanding of `do (x) ->` needs to be extended to this...
Looks like `no-overwrite` doesn't flag this: ``` itemVariable = null grabsItem = do -> {id: itemVariable} = firstStatement.declarations[0] ```
Would make sense to have a mode where `no-return-assign` only flags *explicit* returns Could picture as a new `ignoreImplicit: yes` option Might make sense to then suggest turning this on...
I don't really understand `no-return-assign` to start with, but this seems like it's incorrectly flagging these awaits: ``` x = switch (4) when 2 await winning(1) when 4 await winning(5)...
`jsx-no-bind` is inheriting the error message eg "JSX props should not use arrow functions" when using fat arrows which isn't very helpful in Coffeescript - should change to eg "should...
From my understanding shouldn't be setting eg `parserOptions: ecmaVersion: 6` in tests But there are some stray ones in the tests
I think some people like to just default to using fat arrows for class methods So should be able to use `no-unnecessary-fat-arrow` without having to always flag class methods
This: ``` return (() -> no) if x ``` is getting formatted like: ``` return -> no if x ``` which parses differently