Skip to content

Explore CodeQL or other static code analysis tools #3176

Closed
@jawnsy

Description

@jawnsy

We currently use eslint in our build process, but we might want to explore other tools, such as CodeQL, to catch problematic constructs in our code.

Metadata

Metadata

Assignees

Labels

choreRelated to maintenance or clean upciIssues related to cifeatureNew user visible feature

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions