Upgrade TSLint & TypeScript, disable formatting rules #251
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm wondering why the formatting rules have been disabled? are all they covered by tslint? is it safe to upgrade my project tslint and tslint-react to 6.1.2 and 5.0.0, respectively (I'm currently using tslint 6.1.1 and tslint 4.2.0)? (I know we should migrate to eslint and prettier, but I still want to use them until I found some free times to migration) Thanks |
|
They're removed because we recommend using prettier. You don't have to migrate to eslint to do this, it's pretty easy with tslint-plugin-prettier. The change to remove formatting rules from tslint and tslint-react obviates tslint-config-prettier. Related PR: palantir/tslint#4871 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.