Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration from tslint to typescript-eslint #303

Merged
merged 5 commits into from
Oct 10, 2021

Conversation

joelalejandro
Copy link
Member

Resolves #280.

  • New configuration for eslint, minimum relinting applied.

@joelalejandro joelalejandro added this to the 1.2.0 milestone Oct 9, 2021
@joelalejandro joelalejandro self-assigned this Oct 9, 2021
Copy link
Member

@spersico spersico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I left some comments, but I think it's fine overall

@@ -51,9 +53,14 @@
"@types/pluralize": "^0.0.29",
"@types/supertest": "^2.0.10",
"@types/ws": "^7.4.4",
"@typescript-eslint/eslint-plugin": "^4.33.0",
"@typescript-eslint/parser": "^4.33.0",
"eslint": "^7.32.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why 7.x and not 8.x?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I installed it without version preferences, probably 8.x is still pre-release.

@@ -223,7 +241,7 @@ export default class Application {

resolve();
});
})
}),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this correct? I don't remember this function, but I read https://eslint.org/docs/rules/no-async-promise-executor and this seems like a good catch from the linter isn't it?

Copy link
Member Author

@joelalejandro joelalejandro Oct 10, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The scope of the PR was simply to migrate from one linter to the next. All of the rules I've disabled are improvement opportunities for the codebase, but I didn't want to get them all here, as the PR would become substantially larger in terms of changeset.

We can tackle this in separate issues, one per rule.

@spersico spersico added hacktoberfest-accepted PR accepted for coso refactor Moves or improves code labels Oct 10, 2021
@joelalejandro joelalejandro merged commit acf7a74 into main Oct 10, 2021
@joelalejandro joelalejandro deleted the feature/typescript-eslint branch October 10, 2021 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hacktoberfest-accepted PR accepted for coso refactor Moves or improves code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Replace tslint with typescript-eslint
2 participants