3 commits

Author	SHA1	Message	Date
Zanie Blue	0fc76ba276	Rename applicability levels to Safe, Unsafe, and Display (#7843) ... After working with the previous change in https://github.com/astral-sh/ruff/pull/7821 I found the names a bit unclear and their relationship with the user-facing API muddied. Since the applicability is exposed to the user directly in our JSON output, I think it's important that these names align with our configuration options. I've replaced `Manual` or `Never` with `Display` which captures our intent for these fixes (only for display). Here, we create room for future levels, such as `HasPlaceholders`, which wouldn't fit into the `Always`/`Sometimes`/`Never` levels. Unlike https://github.com/astral-sh/ruff/pull/7819, this retains the flat enum structure which is easier to work with.	2023-10-06 20:50:05 -05:00
Zanie Blue	b64f403dc2	Rename applicability levels to always, sometimes, and never (#7821) ... Following much discussion for #4181 at https://github.com/astral-sh/ruff/pull/5119, https://github.com/astral-sh/ruff/discussions/5476, #7769, https://github.com/astral-sh/ruff/pull/7819, and in [Discord](1159144114), this pull request changes `Applicability` from using `Automatic`, `Suggested`, and `Manual` to `Always`, `Sometimes`, and `Never`. Also removes `Applicability::Unspecified` (replacing #7792).	2023-10-05 13:43:46 -05:00
Micha Reiser	9d16e46129	Add most formatter options to ruff.toml / pyproject.toml (#7566)	2023-09-22 15:47:57 +00:00