Repository navigation
refactor(api): trim schema generation and unify text types - #497
Merged
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.
The official-schema migration retained unused request projections, duplicate text configuration types, redundant field-order overrides, and repeated Go generation. Remove that maintenance overhead while preserving the public contract and stored encodings.
Net change: 216 fewer lines. Validation: generator freshness and nine generator tests; five official-schema tests; public contract, Core API, item, Session and OpenAPI splitter tests; all Core and Go client packages compile; three translation checks. Independent review found no substantiated in-scope issues and independently passed generation and API tests. Official-client CI has passed; remaining CI jobs are still running with no failures observed.