| design.rs |
Lints about the shape of a feature. A feature can pass validation and still be
one that can't be switched off, can't be configured, or can't be filled in
without reading the source. |
17950 |
- |
| documentation.rs |
Lints about descriptions, which are what an experiment owner reads in
Experimenter when deciding what to put in a branch. |
8742 |
- |
| metadata.rs |
Lints about a feature's metadata: who owns it, where it's documented, and where
to file bugs against it. |
5293 |
- |
| mod.rs |
Custom lints for Nimbus feature manifests.
Where validation asks whether a manifest can generate working code, these ask
whether the feature is one an experiment owner can work with. They never stop
code generation, and they're reported by `nimbus-fml lint` alone.
A lint can be silenced by a `no-lint` list on a feature, a top level `no-lint`
list, or `--allow`/`--deny`. |
23006 |
- |
| naming.rs |
Lints about names. Feature ids and variable names are typed by hand into
Experimenter branches, so they should be predictable. |
15807 |
- |