Harmonize output APIs and add wireless XML support - #109
Merged
Conversation
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
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.
What changed
CHANGELOG.md, updated binding examples, and moved the workspace packages to version 0.4.0.Why
Output behavior had drifted between public surfaces: wireless frames could not be rendered as XML, tables overflowed narrow result boxes, syntax highlighting had weak contrast and incomplete language coverage, and error/value representations differed by binding. This makes those surfaces follow one explicit public contract while retaining clearly named legacy renderers for migration.
Impact
The canonical JSON, YAML, CSV, table, and binding representations now share a stable schema. Existing legacy layouts remain available under explicit legacy format names during the 0.4 migration. Wireless XML now uses real decoded transport/application fields and falls back to link-layer identity only when application identity is unavailable.
Validation
cargo test --workspace --all-features --exclude pymbusparsercargo test -p m-bus-parser --features stdcargo clippy --workspace --all-targets --all-features --exclude pymbusparser -- -D warningscargo clippy -p pymbusparser --all-targets --all-features -- -D warningswasm-pack test --headless --firefox(7 browser tests)npm testindocs-ui(WCAG contrast and bundle-size checks)cargo fmt --all -- --checkgit diff --check