Fix native renderer naming and add cross-platform output parity CI - #95
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.
Version 3.2.1 still generates different hook names in JavaScript and native because #94 landed on
codex/rust-codegen-core, notmain. This ports that fix and its parity workflow onto currentmainso the next release can include them.Native follows JavaScript's operation-name collision handling, preserving controller-based hooks instead of falling back to path-based names. Enum names and metadata also match. The port preserves main's newer Zod compilation and enum null handling.
A separate CI workflow generates the checked-in Petstore schema using JavaScript and native on Linux and macOS, then requires identical file lists and exact SHA-256 hashes across all four runs. Files and manifests are retained as artifacts.
Validation: