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
I followed through "Migration to v3" guide and in the end it says following
The new v3 simplifies this by consistently using the string type and limiting available properties. Now, you can only access enum, default, description, examples, and location, ensuring a more focused and practical approach."
My point here is "using the string type".
If we go to the Spec:
Channel Object
Channel Address Expressions
Parameters Object
Parameter Object
The only clue that may lead user to a though that any parameter MUST BE a string it's a type of default and enum properties of Parameter Object, but they are optional.
Shouldn't we point the type of parameter more explicit? Or it's only my problem?
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.
I followed through "Migration to v3" guide and in the end it says following
My point here is "using the string type".
If we go to the Spec:
The only clue that may lead user to a though that any parameter MUST BE a string it's a type of
default
andenum
properties ofParameter Object
, but they are optional.Shouldn't we point the type of parameter more explicit? Or it's only my problem?
The text was updated successfully, but these errors were encountered: