Disable eslint on project basis about coc-eslint HOT 8 CLOSED

How about an option ignoreProjectsWithoutEslintConfig/disableProjectsWithoutEslintConfig? :)

from coc-eslint.

eslint doesn't provide an API for resolve configuration file, so you have to use "eslint.enable": false in your .vim/coc-settings.json inside project folder.
Maybe someone can help to implement such functionality.

from coc-eslint.

I ran into the same problem. +1 on adding an option to ignore projects without an ESLint configuration file. A global default ESLint configuration really just won't work; like @andys8 said, you need different configurations for TypeScript vs JavaScript and node projects vs browser projects.

from coc-eslint.

Checkout https://github.com/neoclide/coc.nvim/wiki/Using-the-configuration-file or create eslint config file in your $HOME

from coc-eslint.

Thanks for the reply.

Thought about those solutions:

• global eslint won't work, because projects are far too different (node/js/ts/frameworks).
• disabling in project would work, but depends on modifying a project even if it's not owned

from coc-eslint.

No, global eslint config file could work as default configuration file.

from coc-eslint.

Yeah, I understand. I think it won't work for my case. E.g. it's a minimal eslint config file. Then opening a typescript based project without eslint file will fail, because its content can't be parsed. This eslint would basically have to match any project (ts, js, browser, node, react, vue).

from coc-eslint.

maybe something like

  autocmd BufNewFile,BufReadPre,BufEnter
        \ */myproject/*.{js,jsx,ts,tsx}
        \   call coc#config('eslint.enable', v:false)
  autocmd BufLeave
        \ */myproject/*.{js,jsx,ts,tsx}
        \   call coc#config('eslint.enable', v:true)

from coc-eslint.