Skip to content

Surface getAssertion unsignedExtensionOutputs to client extension results #250

@AlfioEmanueleFresta

Description

@AlfioEmanueleFresta

Follow-up to #244. That PR fixes decoding of the unsigned extension outputs map at response index 0x08, so assertions no longer fail to parse, but it does not yet surface the map to callers. The decoded outputs are kept on the protocol response and are not merged into the client extension results, because an arbitrary CBOR map does not map cleanly to the typed JSON outputs. A follow-up should add a JSON-safe mapping into the client extension results, with an end-to-end test.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions