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

Add static analysis to build #1993

Open
bctcvai opened this issue Feb 6, 2025 · 0 comments
Open

Add static analysis to build #1993

bctcvai opened this issue Feb 6, 2025 · 0 comments

Comments

@bctcvai
Copy link
Member

bctcvai commented Feb 6, 2025

A few catchable, but unobserved, coding issues have snuck by testing into production.

The build now does formatting checks for both javascript and python. flake8 could be used on the python side to catch more logic errors vs. just formatting related snaffos. eslint could be used on the javascript side for a similar purpose.

We can create sub-issues to this one as each of those insertions is independent. Ideally we add these tools, or similar, into the build such that errors are caught early. Both tools on our code base catch thousands of errors, many innocuous, so either just fixing them or creating ignore rules would be prudent.

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