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.
feat(rpc): decode get_block_by_number maps like transactions (Task 57) #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
feat(rpc): decode get_block_by_number maps like transactions (Task 57) #3
Changes from all commits
b3cc9b0File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keep
Onchain.Block.get_by_number/2error tuples in the standard shape.Line 24 documents
{:error, :block_not_found}. That creates a public API inconsistency versus the project-wide tuple contract. Prefer{:error, {:block_not_found, reason}}(or similar tagged-reason form) for uniform matching.As per coding guidelines
**/*.ex: "Use standard error tuples format:{:ok, result} | {:error, {:tag, reason}}for all public functions."🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normalize
get_by_number/2errors to tagged tuples.These new
{:error, :block_not_found | :pending_block | :invalid_block}branches leak bare atoms from a public API. That makesOnchain.Block.get_by_number/2inconsistent with the repo’s normal error shape and withfind_by_timestamp/2in this same module.💡 One straightforward way to preserve the new behavior without changing the public contract
def get_by_number(block_id, opts \\ []) do with {:ok, block} <- Onchain.RPC.get_block_by_number(block_id, opts) do - summarize_block(block) + case summarize_block(block) do + {:ok, summary} -> {:ok, summary} + {:error, :block_not_found} -> {:error, {:block_not_found, block_id}} + {:error, :pending_block} -> {:error, {:pending_block, block_id}} + {:error, :invalid_block} -> {:error, {:invalid_block, block}} + end end endAs per coding guidelines, "Use standard error tuples format: {:ok, result} | {:error, {:tag, reason}} for all public functions".
Also applies to: 207-217
🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.