Skip to content

fix: use output filename in TypeScript usage imports#2948

Open
AysajanE wants to merge 1 commit into
glideapps:masterfrom
AysajanE:northset/M-105
Open

fix: use output filename in TypeScript usage imports#2948
AysajanE wants to merge 1 commit into
glideapps:masterfrom
AysajanE:northset/M-105

Conversation

@AysajanE

Copy link
Copy Markdown
Contributor

Summary

Use the requested output filename in generated TypeScript usage imports instead of the hard-coded ./file module, with a focused regression.

Change

  • packages/quicktype-core/src/language/JavaScript/JavaScriptRenderer.ts
  • packages/quicktype-core/src/language/TypeScriptFlow/FlowRenderer.ts
  • packages/quicktype-core/src/language/TypeScriptFlow/TypeScriptFlowBaseRenderer.ts
  • packages/quicktype-core/src/language/TypeScriptFlow/TypeScriptRenderer.ts
  • test/unit/typescript-output-filename.test.ts

Checks

  • npm run test:unit -- test/unit/typescript-output-filename.test.ts — passed in a network-isolated container.
  • npm run lint — passed in a network-isolated container.
  • npm run build — passed in a network-isolated container.

Fixes #971


AI assistance was used; I reviewed and own this change.

Verification

Northset proof-of-pass receipt M-105
Contributor self-run; not maintainer verification.

Signed-off-by: Aysajan Eziz <aeziz@northset.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect filename in comment in TS output

1 participant