Consider reverting commit 0cf43e7 that changed the TS record generation from partial to non-partial

[kallevmercury]

After upgrading the library to the latest, we're seeing object types generated as non-partial, like:

{ [k in SomeType]: number };

Instead of:

{ [k in SomeType]?: number };

Unfortunately, this is a breaking change since it affects the client-side API contract. Would it be possible to consider implementing partial map support or possibly reverting the commit that changed this behavior?

Related commit: 0cf43e7

[thomasjm]

the latest

To be clear, this is unreleased code, as I didn't want to commit to a release yet with this.

I think you're right that 0cf43e7 was a mistake. I can't recall why I thought this was a good idea.

Strangely enough, the commit in your PR gives me a segfault when I run it against my internal codebase. I'll try to figure out why.