You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, accessing the message type, if models are generated with Modelina, is not that straightforward, especially if we talk about primitive types.
I think #530 might solve it, as your model directly have access to something like model.type.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Reason/Context
If you create templates for the AsyncAPI generator, you often find yourself in the need of knowing the payload type of a message.
For example, if I want to generate something like:
I would need to template it like so:
Currently, accessing the message type, if models are generated with Modelina, is not that straightforward, especially if we talk about primitive types.
I think #530 might solve it, as your model directly have access to something like
model.type
.The text was updated successfully, but these errors were encountered: