Generate types for unreachable definitions

[relu91]

w3c/wot-thing-description#1319 introduced a schema definition for Form. In principle, this new definition was added to let typescript users have a type for a generic form. Sadly, json-schema-to-typescript does not automatically do it but you have to enable it. This PR enables the generation of unreachable definitions. As you can see on the diff enabling such option causes also the generation of a long list of unwanted comments. I tried to get rid of them without any success. I'm waiting for an answer from the main contributors to remove them, meanwhile, I think we can live with them.

[danielpeintner]

Mhh, sad.... maybe we can do some command afterwards to remove those lines all together.

Anyhow, for the time being I am fine with it. Maybe it gets fixed soon.

[relu91]

Another try could be to write down a description of each rule, that should substitute the awful comment... but there are many rules 🤣

[danielpeintner]

Another try could be to write down a description of each rule, that should substitute the awful comment... but there are many rules 🤣

I don't think it is reasonable. Hence I would go ahead

1. Use as is and hope it gets fixed soon
2. In the worst case a simple search&replace script could do the job since it is always the same text.

[danielpeintner]

Scripting API 2022-01-31

• Can merge as is (maybe clean-up git history), Can be merged afterwards.
• @danielpeintner creates issue to keep track (see Types for unreachable definitions cause unwanted comments #374)

[relu91]

@danielpeintner ready to go