Replies: 3 comments
-
CC @vlad107 I am leaving my current workplace starting from next week and won't be as involved in pbandk's future, but I hope Vlad can overtake my role in communicating with you, @garyp. Feel free to ask him if you need to figure out IOHK's use case for pbandk. |
Beta Was this translation helpful? Give feedback.
-
Is the current options support sufficient to do this, and by chance is there an example for doing so in the existing tests? We're looking at using this in conjunction with Axon Framework. For standard event messages seems we're all set already, but for command messages we need to apply various annotations at the field level. |
Beta Was this translation helpful? Give feedback.
-
FYI: See related discussion #256 |
Beta Was this translation helpful? Give feedback.
-
Motivation
Sometimes it is necessary to mark certain (or all) auto-generated classes with annotations of one's choosing. Some use cases that I can see:
deprecated
option), but there is still no way to deprecate a whole message.@JvmName
/@JvmStatic
. Can be potentially useful for library authors who want to expose proto classes to their users who use plain Java.Implementation
We are particularly interested in use case 1 for which we created a very simple functionality in our own fork: input-output-hk@909c4ff. Now, this might be simple, but it is also ad-hoc. It might be a better option to support a more sophisticated way via proto3 options the way scalapb does it: https://scalapb.github.io/docs/customizations/#adding-annotations.
Beta Was this translation helpful? Give feedback.
All reactions