Skip to content

Tune down defensive try/catch patterns in browser plugin projects #3

@benvinegar

Description

@benvinegar

slop-scan might be overscoring defensive try/catch patterns that are commonly found in browser plugins.

Comment from @garrytan:

https://x.com/garrytan/status/2042258316034965600

I will say in general slop-scan is helpful and I'll probably throw it in my CI tool just to be on the lookout for bad/useless code that Claude/Codex may generate

But simultaneously to that, GStack is a browser plugin and browsers are notorious for needing more rescues to make it work. So, net-net, I accept GStack will likely top your list if for the very reason that it is a browser plugin that requires a lot of rescue blocks to make it work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions