FIX: Issue #511: Does not generate definition for Unions and Intersection Types

[afonsof]

Fix for issue #511

Please:

• Make your pull request atomic, fixing one issue at a time unless there are many relevant issues that cannot be decoupled.
• Provide a test case & update the documentation in the Readme.md

[domoritz]

Could you minimize the changes in this pull request? It's hard to review it otherwise. Thanks!

[afonsof]

Could you minimize the changes in this pull request? It's hard to review it otherwise. Thanks!

There are only 3 lines to be reviewed indeed.

// typescript-json-schema.ts line 1231

if(isRawType && reffedType?.escapedName && (typ as any).types) {
    isRawType = false;
 }

The other ones are new tests and fixes in old tests.

[domoritz]

Great. The formatting changes are throwing me off a bit but I can take a look.

[afonsof]

Great. The formatting changes are throwing me off a bit but I can take a look.

I've just adjusted old files formatting. Now I think it is quite easy to review :)

[domoritz]

Thank you

[afonsof]

@domoritz I have just found a problem. Some types are being generated with |undefined at the end.

[afonsof]

It's possible to solve with a little change

        if (isRawType && (typ as any).aliasSymbol?.escapedName && (typ as any).types) {
            isRawType = false;
        }

[hitesh-parmar]

Hi @afonsof, I would propose to have a possibility to opt-out to use this feature.
We have a very complex schema and a lot of code against this schema which now needs to be adapted to incorporate this change. This is very risky for us. It would be easier to update to a higher version of typescript-json-schema if we have the possibility to disable this feature.