Support @stylistic/eslint-plugin
#283
Comments
|
See #272 |
3 tasks
|
Who can tell me what it takes to complete this Pull Request? This is an important addition. |
This is being handled by PR #272, which should be complete. @JounQin is trying to find the time to complete the review. If you're in a real pinch you can create your own fork of that and pin it as the dependency, then set a reminder to return to mainline later? I know it's not ideal, but at least you'll be able to move forward for the time being. 😅 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
eslint and typescript-eslint have moved their stylistic rules to @stylistic/eslint-plugin.
These are the new rules I believe that need to be turned off:
@stylistic/block-spacing@stylistic/brace-style@stylistic/comma-dangle@stylistic/comma-spacing@stylistic/func-call-spacing@stylistic/indent@stylistic/indent-binary-ops@stylistic/key-spacing@stylistic/keyword-spacing@stylistic/lines-around-comment@stylistic/member-delimiter-style@stylistic/no-extra-parens@stylistic/no-extra-semi@stylistic/nonblock-statement-body-position@stylistic/object-curly-newline@stylistic/object-curly-spacing@stylistic/operator-linebreak@stylistic/quote-props@stylistic/quotes@stylistic/semi@stylistic/space-before-blocks@stylistic/space-before-function-paren@stylistic/space-infix-ops@stylistic/type-annotation-spacingThe text was updated successfully, but these errors were encountered: