guideline_for_datacontenttype_cloudevent_concept_as_enum #193
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PedroDiez
added
enhancement
PedroDiez
requested review from
shilpa-padgaonkar,
rartych,
patrice-conil and
RubenBG7
as code owners
rartych
approved these changes
May 17, 2024
|
If no additional comments i will merge monday next week |
rartych
deleted the
guideline_for_datacontenttype_cloudevent_concept_as_enum
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
By means of this PR, two topics are covered:
datacontenttypecloudevent field value as enum "application\json", consistently with API design guidelines204only, aligned with PR Create subscription-notification-template.yaml #189Which issue(s) this PR fixes:
Fixes #192
Special notes for reviewers:
Changelog input
Additional documentation
N/A