hiero-ledger / hiero-ledger/hiero-consensus-node
Triage all //Future and TODO comments in modularized smart contracts service
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
### Problem
Many comments with //FUTURE or TODO exists in the modularized code base
Also part of this: consider all comments about specific code that's there for mono-service compatibility to see if they're still an issue, should be removed, or what.
### Solution
triage each comment and create issues to address.
### Alternatives
_No response_
```[tasklist]
### Tasks
- [ ] https://github.com/hashgraph/hedera-services/issues/14652
- [ ] https://github.com/hashgraph/hedera-services/issues/14658
- [ ] https://github.com/hashgraph/hedera-services/issues/14661
- [ ] https://github.com/hashgraph/hedera-services/issues/14679
```
Contributor guide
Research direction
Start by inspecting the modularized smart contracts service for //FUTURE, TODO, and mono-service compatibility comments, then review the referenced issues 14652, 14658, 14661, and 14679. Done means every relevant comment has been triaged and follow-up issues have been created where needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, blockchain
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100