Repository navigation
New 4xx rule: after except* FooError as e:, warn on e.attribute for attributes that don't exist on ExceptionGroup #301
Description
This is redundant with a strict typechecker or 100% code coverage, but it's an easy mistake to make when you're migrating error-handling code to use except* and a linter would help for code that doesn't have those other checks.
Reacted by John Litborn
Activity
[-]New rule: after `except* FooError as e:`, warn on `e.attribute` for attributes that don't exist on `ExceptionGroup`[/-][+]New 1xx rule: after `except* FooError as e:`, warn on `e.attribute` for attributes that don't exist on `ExceptionGroup`[/+]jakkdl commentedon Dec 30, 2024
per #334 I think this should go into a new series of 4xx rules
[-]New 1xx rule: after `except* FooError as e:`, warn on `e.attribute` for attributes that don't exist on `ExceptionGroup`[/-][+]New 4xx rule: after `except* FooError as e:`, warn on `e.attribute` for attributes that don't exist on `ExceptionGroup`[/+]jakkdl commentedon Jun 3, 2025
Was implemented in #379 as ASYNC400 except-star-invalid-attribute