feat: Add ContractLog data model and repository interface#75
Open
Twiineenock wants to merge 1 commit intohiero-ledger:mainfrom
Open
feat: Add ContractLog data model and repository interface#75Twiineenock wants to merge 1 commit intohiero-ledger:mainfrom
Twiineenock wants to merge 1 commit intohiero-ledger:mainfrom
Conversation
This commit introduces the core data model (ContractLog) and the ContractLogRepository interface to support querying smart contract events from the Hiero Mirror Node. This establishes the public API surface for the feature, and is aligned strictly with the Hedera Mirror Node REST API JSON responses. Signed-off-by: Twiineenock <Twiineenock@users.noreply.github.com>
Twiineenock
force-pushed
the
feature/smart-contract-logs-api
branch
from
2cd3014 to
51023e9
Compare
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses the first phase of the proposed solution in the linked issue by establishing the core data model and repository interface for the Smart Contract Event and Log API.
To ensure the review process is clean and manageable for mentors, the implementation is being split into logical PRs. This PR specifically focuses on the public API surface:
ContractLogrecord, meticulously mapped to the EVM event log format returned by the Hiero Mirror Node (handling fields liketopics,data, and mappingconsensus_timestampto Java'sInstant).ContractLogRepositoryinterface to provide a high-level abstraction for querying logs byContractId.Subsequent PRs will introduce the
basemodule implementations, followed by the framework-native (Spring Boot/MicroProfile) JSON parsers and pagination handlers.Related issue(s)
Fixes #74
NB
topicslist is wrapped inList.copyOf()) and strict null-safety usingorg.jspecify.annotations.