fix: emit dedicated runtime imports in generated clients - #99
Merged
Conversation
izakgl
approved these changes
Sep 11, 2026
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.
Generated Axios clients imported
RestClientfrom the package root, pulling unrelated runtime exports into consumer builds. Both TypeScript and native generators now emit/axiosfor Axios clients and retain/nativefor native clients. Query imports use/query, including legacy root-path configuration.Shared REST utilities accept native
Headersand unknown errors without Axios types. Documentation lists runtime subpaths, and regression tests inspect emitted imports across both generators. Existing root exports remain available for compatibility.Validation:
Local validation is separate from GitHub CI results.