-
-
Notifications
You must be signed in to change notification settings - Fork 229
chore: Fix current clippy lints #2469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
src/utils/sourcemaps.rs
Outdated
// FIXME: This seems to be a false positive; clippy | ||
// thinks we're doing `contains_key` followed by `insert`, | ||
// but there's no `insert`. | ||
#[allow(clippy::map_entry)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use an expect
:
#[allow(clippy::map_entry)] | |
#[expect(clippy::map_entry)] |
Seems that there is already a PR which fixes this, so with the expect, we'll be alerted to remove the expect
once the PR is released
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good find, I totally missed that, I guess because I was only looking at open issues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately we can't use expect
here because the lint doesn't trip on stable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@loewenheim that is kinda sus, where are we linting with nightly?
I didn't think we linted with nightly in Sentry CLI
Co-authored-by: Daniel Szoke <[email protected]>
This reverts commit 0fbb0b8.
One of them appears to be a false positive, though.