You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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:
pyright
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.
The text was updated successfully, but these errors were encountered: