export aliases are not suported

if interfaces are not directly exported, they are not considered in the schema

This code is well working

export default interface A {...}
export interface B {...}

This one not

interface A {...}
interface B {...}

export default A;
export {B}

The problem is you didn’t consider the export of the sourceFile, but only the member of the source file, then check if they’re flagged as exported, what is not the case.

[mdesousa]

Getting a fix for this would be great! I’m new to ts-json-schema-generator, and was banging my head because my definitions were coming back empty since we always export at the bottom of our files. While the fix is merged, I would suggest to mention this behavior in the readme.

[cspotcode]

It looks like your fork ignores the type and topRef options, instead exporting a schema where each named export of the entrypoint .ts corresponds with a property of the schema. If .ts does export type foo = number; then the schema describes an object with property foo which must be a number.

This is certainly useful, but it must be opt-in; it can’t be the only behavior. In order to make these changes merge-able, I will need to re-enable support for type and topRef. Do you have any suggestions for the cleanest way to do that?