Extensions

[bufdev]

The docs say:

We implement all proto2 features, except for extensions and the text format.

I don't think we can ignore extensions - what does the core js do?

[SyrieBianco]

Tracked internally in TCN-61

[fubhy]

Any news on this? This is currently my main "soft" blocker for implementing message validation (using https://github.com/bufbuild/protoc-gen-validate)

connectrpc/connect-es#270

Is this being worked on or can I lend a hand here? If so, I'd love some pointers (tried to read through the code generator request => descriptor set creation code but am a bit lost to be honest :-)

EDIT:
I am able to get around this via the findCustomMessageOption for now.

[timostamm]

Hey Sebastian, findCustomMessageOption() is indeed the way to go for now!

[fubhy]

Yeah, I built my own version of that before I found that in your code :-D. Sorry for the noise.

[zfedoran]

@fubhy are you able to share what you've done to get message validation running using findCustomMessageOption()?

[rofrankel]

Just commenting to +1 the issue - my use case would benefit from extension support (specifically, message and field options).

[timostamm]

Support for extensions was just released in v1.7.0.

Extensions can be used to retrieve custom Protobuf options from descriptors, for example in a plugin. But it's not possible yet to retrieve options at runtime from generated code. We do have concrete plans for this feature though, and we'll keep the issue #397 updated.