Skip to content

Fix: Keep inbound transaction payloads as JSON objects - #834

Merged
dzikowski merged 4 commits into
mainfrom
fix/fabric-dto-json-object
Sep 17, 2026
Merged

dzikowski merged 4 commits into
mainfrom
fix/fabric-dto-json-object

Conversation

@dzikowski

Copy link
Copy Markdown
Collaborator

Fabric constructed a DTO class from parameter metadata before parseValidDTO ran. Pass the parsed JSON through and mark Fabric parameters as type object so the Submit/Evaluate input class is the one that is instantiated.

dzikowski and others added 3 commits September 17, 2026 13:50
Fabric constructed a DTO class from parameter metadata before parseValidDTO ran. Pass the parsed JSON through and mark Fabric parameters as type object so the Submit/Evaluate input class is the one that is instantiated.

Co-authored-by: Cursor <cursoragent@cursor.com>
Keep the chain-test copy in sync so inbound DTOs stay plain objects after Fabric schema type is forced to object.
Fabric keys transaction metadata by method name, so the same name on two contracts can bind the wrong DTO. parseValidDTO does the real parse.
@dzikowski
dzikowski enabled auto-merge (squash) September 17, 2026 15:12
@dzikowski
dzikowski merged commit 059f4c0 into main Sep 17, 2026
19 of 20 checks passed
@dzikowski
dzikowski deleted the fix/fabric-dto-json-object branch September 17, 2026 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants