correctly document this function ( it thinks it is `raw_hash` )
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- documentation
Research direction
Read the linked lines 92–96 in framework_crates/bones_schema/src/raw_fns.rs and inspect the function's existing documentation, which appears to identify it as raw_hash. Update the documentation to describe the function correctly. Done when its documentation matches the function; the issue does not name a test to run.
Written by the indexing model from the issue text.
Description
This issue was generated by todo-issue based on a TODO comment in cd62a2f1ccdb00df6003af65f01edb26914c8c33.
- Dominant language
- Rust
- Stars
- 314
- Forks
- 26
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fishfolk/bones
-
code:todo
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
code:todo
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
code:todo
Difficulty 3/5 Half a day Newbie friendliness 48/100
-
code:todo
Difficulty 3/5 1-2 days Newbie friendliness 67/100
-
code:todo
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Similar issues
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pedrovgs/UseCaseCoverage#23 ·
-
area: library data-loss tier: p0 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day