Open MQ-xz opened 1 year ago
@MQ-xz Could it be due to the fact that your type
is named type
? What if you change your top level type
value to something like kind:
? Perhaps that would rule out the potential for a conflict on that keyword?
I don't think so, since when removing the string from enum it's working fine. Also look at that error message. the string shows like a function ("String()") as an option in it.
Also I think the issue is only raised when we use a string as a type.
Schema
yml code
error got