Open JayWhite2357 opened 1 week ago
/attempt #163
with your implementation plan. Note: we will only assign an issue if you include an implementation plan with a time estimate. Additionally, to be assigned an issue, you must have previously contributed to the project. You can still work on an issue and submit a PR without being assigned./claim #163
in the PR body to claim the bountyThank you for contributing to spaceandtimelabs/sxt-proof-of-sql!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🟢 @onyedikachi-david | Sep 26, 2024, 4:00:19 AM | WIP |
🟢 @Gmin2 | #188 |
/attempt #163
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@onyedikachi-david | 7 bounties from 4 projects | JavaScript, Shell |
Cancel attempt |
can i get assigned to this @JayWhite2357 ?
@Gmin2 Yes. Can you please include an implementation plan with a time estimate?
FYI: to avoid confusion on this. It looks like there is a mismatch between my original GitHub comment and the adjusted bounty amount. I just deleted the GitHub comment.
EDIT: looks like that doesn't work very well.
doing it by eod !
/bounty $200
💡 @Gmin2 submitted a pull request that claims the bounty. You can visit your bounty board to reward.
Background and Motivation
In order to improve documentation and identify possible panics, we should enable clippy lints that warn when a function that panics but does not document this behavior.
Requested Changes
clippy::missing_panics_doc
lint.#![cfg_attr(test, allow(clippy::missing_panics_doc))]
in order to not warn ontest
-only functions.check-private-items = true
option.It is ok for this to be done in separate PRs. (e.g. one PR could enable the lint, and simply write
TODO: add panic docs
everywhere the warning appears. NOTE:allow(clippy::missing_panics_doc)
should only be used if apanic
is actually impossible.