feat(thrum): views.rs as protocol source with generated mirrors - #59
Merged
Merged
Conversation
Canonical per-chi body structs live in thrum-core/src/views.rs; codegen
parses them with syn and emits protocol.{ts,py,go} so the three clients
cannot drift. thrum-core's build fails if any chi lacks a body view.
Golden fixture (15 tones) locks the wire; go/python parse tests and
Crockford-52 rid() parity (hum_identity vectors) run in CI via wire.yml.
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
1 participant
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.
Rust is the source of truth; JSON is just the wire serialization.
Checks: codegen --check clean, thrum-core 55 tests, codegen 7, go ok, python 6, TS vectors verified via bun.