We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem description API Design Guidelines requirement is that datacontenttype field is media-type that describes the event payload encoding, must be application/json for CAMARA APIs In https://github.com/camaraproject/Commonalities/blob/main/artifacts/notification-as-cloud-event.yaml it is defined as follows:
datacontenttype
application/json
datacontenttype: type: string description: 'media-type that describes the event payload encoding, must be "application/json" for CAMARA APIs'
Possible evolution Define required value as enum - as the only possible value is "application/json"
Alternative solution
Additional context The similar specversion field is defined as enum with PR:
specversion
The datacontenttype field is optional , specversion field is mandatory
The text was updated successfully, but these errors were encountered:
Agree to follow same approach and define value as enum
Sorry, something went wrong.
+1
Will be generating PR this week
Successfully merging a pull request may close this issue.
Problem description
API Design Guidelines requirement is that
datacontenttype
field is media-type that describes the event payload encoding, must beapplication/json
for CAMARA APIsIn https://github.com/camaraproject/Commonalities/blob/main/artifacts/notification-as-cloud-event.yaml it is defined as follows:
Possible evolution
Define required value as enum - as the only possible value is "application/json"
Alternative solution
Additional context
The similar
specversion
field is defined as enum with PR:The
datacontenttype
field is optional ,specversion
field is mandatoryThe text was updated successfully, but these errors were encountered: