Skip to content

Feature/issue 11 json field type#14

Merged
haumacher merged 2 commits intomainfrom
feature/issue-11-json-field-type
Mar 25, 2026
Merged

Feature/issue 11 json field type#14
haumacher merged 2 commits intomainfrom
feature/issue-11-json-field-type

Conversation

@haumacher
Copy link
Member

Fixes #11

haumacher and others added 2 commits March 25, 2026 11:45
Verify that the import mechanism supports embedding messages from one
protocol as field types in another (not just cross-file extends).
Two proto files: shared.proto defines Address/Coordinate, composite.proto
imports them and uses them as fields in Person and DeliveryOrder.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Add a `json` primitive type to msgbuf that represents an opaque JSON value.
In JSON format, the value is written natively without string-wrapping.
For binary serialization, values are wrapped in a JsonValue message hierarchy
(JsonString, JsonLong, JsonDouble, JsonBoolean, JsonNull, JsonArray, JsonObject).

Also fixes a pre-existing bug where map fields were not serialized in binary
format (binaryWriteValue had a TODO for MapType).

Closes #11

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@haumacher haumacher force-pushed the feature/issue-11-json-field-type branch from 8250da2 to dbcdd21 Compare March 25, 2026 10:47
@haumacher haumacher merged commit 346d3f5 into main Mar 25, 2026
@haumacher haumacher deleted the feature/issue-11-json-field-type branch March 25, 2026 10:47
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.

Native JSON value type (avoid string-wrapping of structured data)

1 participant