types/strict
The type checker runs in strict mode
A capability: each stack checks it with its own tools. Implemented for cpp, dotnet, flutter, go, hugo, java, kotlin, node, php, python, rust.
Combine: all. Every implementation that runs must pass: each stack in the repository meets the requirement with its own tools.
| Severity | warning |
| Tiers | 1, 2 |
| Stacks | any |
| Scope | each |
| Kind | capability |
| Source | library v0.5.0 |
| Selected by | fleetlint-recommended@v0.5.0 |
Requirement
Where the stack has an optional or configurable type checker, it runs in its strictest mode, configured in the repository.
Why
A lenient type checker lets untyped and implicitly dynamic values through, which is where the bugs it exists to catch hide.
Fix
Switch the type checker to strict mode (see https://fleetlint.org/stacks/).
Agent instruction: Switch the type checker to strict mode and list the errors that appear instead of adding ignores.
Sources
- https://fleetlint.org/baseline/#static-analysis (convention)
Generated by fleetlint docs from catalog v0.5.0.