-
Notifications
You must be signed in to change notification settings - Fork 889
Split out formatting rules into a separate package #3592
Comments
That means you want to publish a separate npm package like Btw. if you want to publish packages with |
I'd like to convert this to a monorepo; I think tracking all issues together in one repo is a good workflow we should retain. Thanks for the offer about the |
💀 It's time! 💀TSLint is being deprecated and no longer accepting pull requests for major new changes or features. See #4534. 😱 If you'd like to see this change implemented, you have two choices:
👋 It was a pleasure open sourcing with you! If you believe this message was posted here in error, please comment so we can re-open the issue! |
🤖 Beep boop! 👉 TSLint is deprecated 👈 (#4534) and you should switch to typescript-eslint! 🤖 🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋 |
Following up on my comments here: #3395 (comment)
I'd like to separate these rules and disable them in the
tslint:recommended
configuration so that it's easier to use prettier with tslint. Prettier does a great job of formatting and I'd rather invest time & energy in other tslint rules that are not formatting-related.The text was updated successfully, but these errors were encountered: