test: enable Swift and TypeScript schema CI coverage - #3449
Open
schani wants to merge 1 commit into
Open
Conversation
Generated-output differences23 files differ — 0 modified, 20 new, 3 deleted |
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.
Enable Swift JSON/schema CI on macOS and add TypeScript schema fixtures to the existing TypeScript job; both previously disabled groups now pass. Broaden Swift final/hashable, TypeScript type/const, and Dart from-map option coverage; remove an obsolete Swift schema-comparison skip.
Validation: 489 Swift, Dart, and TypeScript fixtures passed; the restored Swift miscellaneous comparison passed; workflow YAML parsed and fixture groups verified; formatting checked. No production changes.