Open LoicPoullain opened 7 months ago
Hello @LoicPoullain, I am interested in contributing to this issue. Does this issue still has a priority?
Quickly glancing over the description, I believe that I should be creating a fork from the master branch?
And the tool that I should be using would be the one mentioned in the second last paragraph of this comment. https://github.com/palantir/tslint/issues/4534#issue-413722441
Hello @deepanshu44
I am interested in contributing to this issue. Does this issue still has a priority?
Yes, you can take this one if you wish!
Quickly glancing over the description, I believe that I should be creating a fork from the master branch?
Yes
And the tool that I should be using would be the one mentioned in the second last paragraph of this comment. palantir/tslint#4534 (comment)
Perhaps. I have never migrated a project from TSLint to ESLint myself. But this has already be done in this PR to migrate the applications generated by createapp
form TSLint to ESLint. The TSLint rules that were used by createapp
are the same that the ones currently used for the framework linting.
Issue
TSLint is (unfortunately) no longer maintained and framework linting should be migrated to ESLint.
This was done four years ago in this PR for projects generated with Foal. This means that, when executing the
createapp
command, new projects generated with this command use ESLint.But the framework monorepo itself has not yet been migrated to ESLint. This is a technical debt that should be resolved.
Guidelines
v4-5-0
. Otherwise, it should be created frommaster
. Not only will this facilitate the migration to ESLint, it will also avoid the need for additional work later on to manage ESLint dependencies with the new dependency system.~Notes
packages/cli/src/generate/specs/app/.eslintrc.js
andpackages/cli/src/generate/templates/app/.eslintrc.js
used byfoal createapp
to generate new projects may cause problems.