feat: add an option to disable Exact types

[aikoven]

Closes #454

[stephenh]

I'm still a little bummed about not finding a way for your mapped types to keep these, but am not coming up with anything ... i.e. a way to pass long / "look up" the "appropriate" / "contextual" DeepPartial from a given message.

On another project, I've made fake properties, i.e.:

class Foo { 
  __types: { encoder: FooEncoder, decoder: FooDecoder }
}

And then always just set __types: null! because it's not actually used at runtime, but is just a way for mapped types to look into __types and grab what it needs.

For that project, the __types approach was more appropriate, but it seems more icky here, sitting on protobuf message types... 🤷

But yeah, this is a cheap option to add, so why not/makes sense. Maybe add it to the readme, just in case others run into issues with Exact?

[aikoven]

The hardest problem is preserving the trick with generic parameter required for Exact in mapped type.

Things might get better if/when TypeScript supports exact types natively :)

But yeah, this is a cheap option to add, so why not/makes sense. Maybe add it to the readme, just in case others run into issues with Exact?

I've updated the readme, could you review it please?

[stephenh]

Looks great, thanks @aikoven !

[stephenh]

🎉 This PR is included in version 1.97.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀