hiero-ledger / hiero-ledger/hiero-consensus-node
Output wires and transformers should be remember by the wiring framework and not the creators
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
Components in the wiring framework do not store output wires and transformers.
That forces anyone wiring things together to store references to them locally so they are not lost.
If those references need to be stored for the whole lifecycle of the application, it requires that we store them alongside the components, creating the need for records like:
* RunningEventHashOverrideWiring
* PcesReplayerWiring
* ConsensusWiring
A possible solution would be that the ComponentWiring class has functionality to store these typical output wires and transformer types internally. We could have a class like RecordOutputComponentWiring that adds this functionality for components that output records. Then the transformers stored could be retrieved from the field. Or it could be part of the task schedulers.
Contributor guide
Research direction
Start by reading ComponentWiring and the existing RunningEventHashOverrideWiring, PcesReplayerWiring, and ConsensusWiring records to understand how output wires and transformers are currently retained. Compare whether storage belongs in a RecordOutputComponentWiring abstraction or task schedulers. Done means the wiring framework retains these references for the component lifecycle and existing creator-specific records are no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100