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
Can I kindly ask you to help me reporting this bug / initiate an inquiry ? I am not sure where I should send this info?
Feel free to copy pate / reference this comment where needed.
FYI, I think I have a better understanding of the cause regarding enums being between
' " ... " '
.generated yaml is:
No problem here:
messageStatus: OK
is correct, i.e.,OK
is NOT surrounded by single and double quote@Schema(enumAsRef = true)
on theMessageStatus
class, then the generated yaml is:So, having enum being Component, seems to 'trigger' the bug (I guess this is a bug...?),
i.e., turn
into
Which is NOT correct
@Schema(enumAsRef = true)
to@Schema(enumAsRef = true, example = "OK")
the generated yaml is now:
So, exactly the same as before EXCEPT FOR
messageStatus: OK
which does not have the' " ... " '
around the enum anymore.I could not find this bug being reported in https://github.com/asyncapi/parser-js/issues?q=is%3Aissue+is%3Aopen+enum
I am not sure where / how to report this bug.
Can I kindly ask you to help me reporting this bug / initiate an inquiry ? I am not sure where I should send this info?
Feel free to copy pate / reference this comment where needed.
Thanks.
Pascal
Originally posted by @pdalfarr in #534 (comment)
The text was updated successfully, but these errors were encountered: