docs(wasm-utxo): document structured error conventions - #386
Merged
OttoAllmendinger merged 1 commit intoSep 8, 2026
Merged
Conversation
Document the typed error boundary, stable JavaScript error codes, and the Ok(false) versus structured-error contract for new wasm-utxo APIs. Link the package architecture guides to the repository convention so new WASM methods do not extend the legacy StringError pattern. Refs: CSHLD-1681
veetragjain
approved these changes
Sep 8, 2026
OttoAllmendinger
marked this pull request as ready for review
September 8, 2026 13:52
OttoAllmendinger
deleted the
otto/CSHLD-1681-document-structured-error-conventions
branch
September 8, 2026 13:52
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.
Document the typed error boundary, stable JavaScript error codes, and the
Ok(false) versus structured-error contract for new wasm-utxo APIs. Link the
package architecture guides to the repository convention so new WASM methods
do not extend the legacy StringError pattern.