bitshares / bitshares/bitshares-core
Add messages to FC_ASSERT's
Open
1b User Story
2b Gathering Requirements
3c Enhancement
6 API
code cleanup
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 660
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 26
Description
Many assertions in the code lack of a message describing why the exception is thrown, thus end-users and UI devs often get confused.
Contributor guide
No contributing guide indexed for this repository
Research direction
Search the C++ codebase for FC_ASSERT usages and identify assertions that lack explanatory messages. Review the surrounding validation paths to understand what each exception communicates. Done means the targeted assertions provide useful messages for end-users and UI developers, with the affected checks verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100