hiero-ledger / hiero-ledger/hiero-consensus-node
Update `HookDispatchTxBody` with expected extension point
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
As we add more hook extension points, a nice belt-and-suspenders safety measure will be to add a field [here](https://github.com/hiero-ledger/hiero-consensus-node/blob/main/hapi/hedera-protobuf-java-api/src/main/proto/services/hook_dispatch.proto#L38) for the "expected extension point",
```
/**
* Details the execution of a hook.
*/
message HookExecution {
...
/**
* The extension point the target hook MUST implement.
*/
HookExtensionPoint extension_point = 3;
}
```
Contributor guide
Research direction
Start with hapi/hedera-protobuf-java-api/src/main/proto/services/hook_dispatch.proto at the referenced HookExecution definition. Confirm how HookDispatchTxBody and HookExecution are represented, then add the expected extension-point field described in the issue. Done means the schema contains the documented field and the Java protobuf API builds successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100