CATcher-org / CATcher-org/CATcher

Migration from tslint to an alternate static analysis tool

Open
#550 3 comments 0 reactions 0 assignees View on GitHub
aspect-CodeQuality p.Low
Dominant language
TypeScript
Stars
92
Forks
85
PR merge metrics
No merged PRs in 30d

Description

Given that [tslint is deprecated](https://github.com/palantir/tslint#tslint) and that it is important to note that tslint does not catch indentation errors as mentioned in an example [here](https://github.com/CATcher-org/CATcher/pull/538#discussion_r563040956)

It will be good to have that we migrate from tslint to another static analysis tool such as [eslint](https://github.com/eslint/eslint) to maintain code quality within our code base.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the repository's existing TSLint configuration and usage across the TypeScript codebase, then compare the migration options, including ESLint. Done means TSLint has been replaced by an agreed static analysis tool and the code-quality checks include indentation errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, typescript
Domain
tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.