refactor: replace old getLogs with sdk.getLogs v3 #400
Conversation
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
fix wrong order of args in README.md file example
0x4r45h
force-pushed
the
feat/use-new-sdk-getLogs-method
branch
from
014c124 to
4e90762
Compare
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.
Related to #393
This change replaces the old getLogs method with the new sdk.getLogs (v3) method as a drop-in replacement, requiring minimal changes.
If approved, I can work on integrating it into other parts of the codebase to fully leverage the SDK.
Tested with a few chains, and the results look consistent. For example: