fix: update calculateAtomId docs to require Hex type input#81
Open
jonathanprozzi wants to merge 1 commit into
Open
fix: update calculateAtomId docs to require Hex type input#81jonathanprozzi wants to merge 1 commit into
jonathanprozzi wants to merge 1 commit into
Conversation
The calculateAtomId function requires a Hex type (0x-prefixed string) as input, not a plain string. Updated all examples to use toHex() from viem to convert strings before passing to calculateAtomId. https://claude.ai/code/session_01M9noPs9691tdGVHwPdbxwT
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
2 participants
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
calculateAtomIdfunction signature to show it requiresHextype input instead ofstringtoHeximport from viem to all code examplescalculateAtomId()calls to usetoHex()to convert strings to hex formatThis fixes the documentation mismatch where examples showed passing plain strings like
'developer'or'NewAtom', but the actual SDK implementation requires a hex-encoded string (0x-prefixed).Files changed:
docs/_data/intuition-sdk/atoms-guide.mddocs/_data/intuition-sdk/examples/find-existing-entities.mdTest plan
Slack thread: https://intuition-systems.slack.com/archives/C0AFT55SQF4/p1776457332794299?thread_ts=1776456051.552199&cid=C0AFT55SQF4
https://claude.ai/code/session_01M9noPs9691tdGVHwPdbxwT