On Tuesday, 8 June 2021 22:15:36 CEST, Derek Perez wrote:
well known types are not extendable in this way, currently.
By their nature, they are not designed to support custom types as they
wouldn't exactly be well known by our definition of well known (meaning,
known to all).
Hello,
I am well aware of that fact!
My idea was "If it is possible to do that with Google's well-known types,
surely I can use the same method to have a better API for our internal
types".
However, it appears that the enhanced support for well-known types is
hardcoded into the library. Would the right path here be to write a
compiler plugin, to adjust the generated code in a similar manner?
--
Raphaël Barrois
On Tue, Jun 8, 2021 at 12:35 PM Raphaël Barrois <[email protected]>
wrote:
Hi,
I am currently looking at ways of extending the generated
code, in order to
add some helpers for some messages which map to standard types in our
codebase (think UUID, IPv6 — akin to the extended features awarded to the
well-known types). ...
--
You received this message because you are subscribed to the Google Groups "Protocol
Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/protobuf/65bc9dce-2740-424b-858d-6727d2e0a0f8%40gmail.com.
