Dylan b6bd32d9dc Track t-strings and f-strings for token-based rules and suppression comments (#20357) ... Our token-based rules and `noqa` extraction used an `Indexer` that kept track of f-string ranges but not t-strings. We've updated the `Indexer` and downstream uses thereof to handle both f-strings and t-strings. Most of the diff is renaming and adding tests. Note that much of the "new" logic gets to be naive because the lexer has already ensured that f and t-string "starts" are paired with their respective "ends", even amidst nesting and so on. Finally: one could imagine wanting to know if a given interpolated string range corresponds to an f-string or a t-string, but I didn't find a place where we actually needed this. Closes #20310		2025-09-12 13:00:12 -05:00
..
fixtures	Track t-strings and f-strings for token-based rules and suppression comments (#20357)	2025-09-12 13:00:12 -05:00
package	Rename ruff crate to ruff_linter (#7529)	2023-09-20 08:38:27 +02:00
project	Rename ruff_cli crate to ruff (#9557)	2024-01-16 17:47:01 -05:00
__init__.py	[pylint] (Re-)Implement import-private-name (C2701) (#9553)	2024-01-16 14:03:11 -05:00
disallowed_rule_names.txt	Rename ruff crate to ruff_linter (#7529)	2023-09-20 08:38:27 +02:00