ruff/crates/red_knot
Micha Reiser 678b0c2d39
[red-knot] Resolve `Options` to `Settings` (#16000)
## Summary

This PR generalize the idea that we may want to emit diagnostics for 
invalid or incompatible configuration values similar to how we already 
do it for `rules`. 

This PR introduces a new `Settings` struct that is similar to `Options`
but, unlike
`Options`, are fields have their default values filled in and they use a
representation optimized for reads.

The diagnostics created during loading the `Settings` are stored on the
`Project` so that we can emit them when calling `check`.

The motivation for this work is that it simplifies adding new settings.
That's also why I went ahead and added the `terminal.error-on-warning`
setting to demonstrate how new settings are added.

## Test Plan

Existing tests, new CLI test.
2025-02-10 15:28:45 +01:00
..
docs Update pre-commit dependencies (#14719) 2024-12-02 06:02:56 +00:00
src [red-knot] Resolve `Options` to `Settings` (#16000) 2025-02-10 15:28:45 +01:00
tests [red-knot] Resolve `Options` to `Settings` (#16000) 2025-02-10 15:28:45 +01:00
Cargo.toml Tidy knot CLI tests (#15685) 2025-01-23 14:06:07 +01:00
build.rs [red-knot] Add version command (#15823) 2025-02-02 18:56:51 +00:00