docs: document encodeCallMsg validation and logTriggerConfig helper#3517
Draft
docs: document encodeCallMsg validation and logTriggerConfig helper#3517
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Add caution about silent data corruption when bypassing encodeCallMsg - Document field-context error messages in encodeCallMsg - Add logTriggerConfig() as recommended approach for log trigger setup - Restructure EVM log trigger docs to prioritize logTriggerConfig over manual hexToBase64
wentzeld
force-pushed
the
docs/sdk-evm-helpers
branch
from
e2095a5 to
d4d15b1
Compare
Contributor
Author
|
Needs this PR to be merged first smartcontractkit/cre-sdk-typescript#201 |
3 tasks
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.
Summary
encodeCallMsg()encodeCallMsg()logTriggerConfig()as recommended approach for log trigger setuplogTriggerConfig()over manualhexToBase64()Files changed
evm-client-ts.mdx—encodeCallMsgcaution + validation docs,logTriggerConfighelper referenceevm-log-trigger-ts.mdx— Restructured to recommendlogTriggerConfig(), manual approach moved to collapsible section