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

Suggestion to expand 2.2 (use a linter) #10

Open
aholmes opened this issue Feb 6, 2023 · 0 comments
Open

Suggestion to expand 2.2 (use a linter) #10

aholmes opened this issue Feb 6, 2023 · 0 comments

Comments

@aholmes
Copy link

aholmes commented Feb 6, 2023

In Code development 2.2 it is suggested to use a linter. This item might benefit from expanding on "linter" and suggesting other tools in addition. An example: rather than "use an appropriate linter," perhaps the wording "use available code quality tools such as linters, type checkers, and automatic code scanning" explains more about this tooling.

Some examples of other tools that might be included in this list:

  • The Python type checker pyright
  • TypeScript with the appropriate configuration and checks
  • Perhaps indicating some linters like styler, flake8, or black
  • Tools to calculate cyclomatic complexity or change risk anti-patterns

Expanding on "automated" may be important here. There are several levels to automation, including IDE integrations, Git commit hooks, CI/CD pipelines, and so on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant