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

Refactor unstructured codebase and integrate linting checks #72

Open
YashKumarVerma opened this issue May 17, 2020 · 2 comments · May be fixed by #76
Open

Refactor unstructured codebase and integrate linting checks #72

YashKumarVerma opened this issue May 17, 2020 · 2 comments · May be fixed by #76

Comments

@YashKumarVerma
Copy link

Since the judege-taskmaster and ** judge-api** codebases are used in production applications, the code needs to follow particular standards and guidelines, which can greatly increase its maintainability as a community project.

Therefore linters should be set as would be done under coding-blocks/judge-taskmaster#41 up to force standard code guidelines on the repository.


Working on it, would send PR as soon as the issue acknowledged.

@jatinkatyal13
Copy link
Contributor

Linters sure are required tooling for production projects to maintain consistency.

Following will be your TODOs

  • Setup TS Lint (Refer this and this)
  • Setup Prettier
  • Add linting script in package.json
    • lint script
    • lint:fix script

@YashKumarVerma
Copy link
Author

cool, working on it !

@prathambatra prathambatra linked a pull request May 24, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants