Version Packages#1766
Merged
Merged
Conversation
14faa6b to
2e9ba45
Compare
2e9ba45 to
aa89ed1
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
swagger-typescript-api@13.11.0
Minor Changes
f5cb2daThanks @js2me! - Fix external file$refresolution and add cleaner schema naming for split OpenAPI specs.Bug fixes
./SidecarConfig.yaml,./models/sidecar-config.yaml) without producing ghost types such asSidecarConfigYamlthat were referenced in generated output but never exported.models,definitions, and.as schema components instead of misclassifying them as OpenAPI component sections..yaml,.yml, and.jsonextensions.components.schemas.export interfacedeclarations (e.g. multipleNovaEntityNovaEntity) and TypeScript merge conflicts.pathItemsas a validcomponentssection when resolving JSON pointer segments.New option
preferExistingSchemaNamesForExternalRefs(CLI:--prefer-existing-schema-names-for-external-refs).When enabled, if an external schema file name matches an existing local component name (e.g.
./Specification.yaml→Specification), the generator reuses the local schema name instead of emitting redundant names likeSpecificationSpecificationorNovaEntityNovaEntity.Local
$ref-only components are eagerly resolved before parsing.Tests
paths-2regression tests for remote OpenAPI specs with relative cross-file refs (CICD Spec Manager fixture).paths-2-prefer-existing-schema-namestests for the new naming option, including strict TypeScript checks of generated snapshot output viatsc.Patch Changes
6d00192Thanks @Upgrade220! - FixContentTypein http-client not respectingenumStyle: "union". It now generates a plain type alias instead of an enum, and all call sites emit string literals instead ofContentType.Jsonetc.