Feature Request
Is your feature request related to a problem? Please describe.
As of now(until the export type PR gets merged), we have exportKind: value for values as well as types. This creates some problems in parsing and then transforming the typescript code correctly.
This feature is part of #10981.
Describe the solution you'd like
Add exportKind: "type" for type-only export decarations like export type A = 2 or export interface B {}, namespaces etc.
"type":
- Type aliases:
export type A = 2
- Interfaces:
export interface B {}
- declare X:
export declare const x: number;
"value":
- Enums:
export enum E {}
- Namespaces:
export namespace X.Y {}
Teachability, Documentation, Adoption, Migration Strategy
Maybe we need to tweak the parser and then the generator with some conditions. Excited to work on it.
Feature Request
Is your feature request related to a problem? Please describe.
As of now(until the
export typePR gets merged), we haveexportKind: valuefor values as well as types. This creates some problems in parsing and then transforming the typescript code correctly.This feature is part of #10981.
Describe the solution you'd like
Add
exportKind: "type"for type-only export decarations likeexport type A = 2orexport interface B {},namespacesetc."type":
export type A = 2export interface B {}export declare const x: number;"value":
export enum E {}export namespace X.Y {}Teachability, Documentation, Adoption, Migration Strategy
Maybe we need to tweak the parser and then the generator with some conditions. Excited to work on it.