-
-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should defaultContentType have a default? #319
Comments
I don't think it should be mandatory, |
I agree with @derberg, like the idea of keeping the AsyncAPI file as simple as possible (default over mandatory) 👍 |
Yes, I agree too. Thanks, folks! |
This issue has been automatically marked as stale because it has not had recent activity 😴 |
Is there any of you who wants to champion this? 🙂 Or can we consider this issue as |
defaultContentType doesn't have a default value and it's not listed on the AsyncAPI Object, even though it's at root level and must be there.
Should we make this field mandatory or have a default value of, for example,
application/json
?Thanks, @jstoiko for your work on the TCK, it helped raise the issue.
The text was updated successfully, but these errors were encountered: