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
Right now the originalInput property in the MetaModel is a relic that over-served its purpose in its current form.
Here are the current problems with it:
It's impossible to determine the type of the input that builds the model. I.e. it could be an AsyncAPI Schema, or Avro, the only way to know is for each time you access it determine it by interpretation.
If you do end up interpreting the value it's near impossible to know the type as it's all internal in Modelina without having any rules on what it may be.
These two problems make it hard to use the values when needed in the presets.
Ideally, any important values should be part of the MetaModels, but the originalInput should always be there as a backup for users. It should also be possible for users to extend the originalInput types to custom ones in order to support that users can create their own models from scratch.
Therefore I propose we change this in the next major version as this will be a breaking change.
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
Right now the
originalInput
property in the MetaModel is a relic that over-served its purpose in its current form.Here are the current problems with it:
These two problems make it hard to use the values when needed in the presets.
Ideally, any important values should be part of the MetaModels, but the
originalInput
should always be there as a backup for users. It should also be possible for users to extend the originalInput types to custom ones in order to support that users can create their own models from scratch.Therefore I propose we change this in the next major version as this will be a breaking change.
The text was updated successfully, but these errors were encountered: