Skip to content

fix: remove unused enum value - #191

Merged
AnderBiguri merged 1 commit into
CambridgeCIA:mainfrom
TimLeach635:fix/enum-masking
Sep 29, 2026
Merged

AnderBiguri merged 1 commit into
CambridgeCIA:mainfrom
TimLeach635:fix/enum-masking

Conversation

@TimLeach635

Copy link
Copy Markdown
Contributor

Previously, these two enums were both being represented by the same underlying integer, meaning they couldn't be differentiated from each other. This fix means they can now actually be separated!

Co-authored by Claude Code (Sonnet 5), reviewed by me

@AnderBiguri

Copy link
Copy Markdown
Member

Ah, but these are the same thing, with a different name. I think actually removing NOISY_RECON may be best instead

@TimLeach635

Copy link
Copy Markdown
Contributor Author

Ah, but these are the same thing, with a different name. I think actually removing NOISY_RECON may be best instead

Fantastic - see, this is exactly the kind of thing AI fails to spot!! I'll give removing NOISY_RECON a go and report back

@TimLeach635 TimLeach635 changed the title fix: stop enums masking fix: remove unused enum value Sep 16, 2026
@TimLeach635

Copy link
Copy Markdown
Contributor Author

It's been ages, but I've now done this! @AnderBiguri

@AnderBiguri
AnderBiguri merged commit 571c2ca into CambridgeCIA:main Sep 29, 2026
1 check passed
@TimLeach635
TimLeach635 deleted the fix/enum-masking branch October 12, 2026 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants