Sahin Yort

I am not sure if that is the correct approach here as we tried that one before. The best would be optional getters which is not supported by typescript yet....

I have no problem whatsoever with the approach above. there are some typescript limitations that prevent us from doing this. The problem with getter setter types is that they can’t...

https://www.typescriptlang.org/play?#code/MYGwhgzhAECyCmUwHN7QN4ChrQvALtPovgBQBuYIArvAFy74BOAlgHbLQA+01bAJvABm7ePwCUGHAF9s0VIWIQy4hstYcMs6UA Also see: https://github.com/microsoft/TypeScript/issues/2521 https://github.com/microsoft/TypeScript/pull/42425

it is going to take a while this gets stabilized. then we can revisit the options.

> Sorry, I still don't see the need to wait for new TypeScript features. Maybe I'm wrong. You are right. This definitely should be fixed. Would be happy to see...

Though this is going to be a breaking change. so I have to find a way to land this without annoying everyone.

> 7. [Well-Known Types](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf), e.g. `Int32Value` > For unset singular scalar types you (as a receiver / consumer of a message) cannot detect if the sender / producer of the...

that would be possible yes. via `SourceCodeInfo` but we don’t support it yet.

At the moment, it doesn’t seem to be possible to use this; See: https://github.com/bazelbuild/rules_proto/issues/40

> In the readme it says that there is partial web support. What does this mean exactly? Can I use this library in a browser client? Thanks! Hey. Let me...