-
Notifications
You must be signed in to change notification settings - Fork 56
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
Modified content-type to abide by attribute naming conventions for cloudevents #232
Conversation
Hey @vivjd, thx for opening the PR. Unfortunately your change is not really what the desired behavior should be. I've mentioned the desired one here: #211 (comment) So if you're up for changing this to comply with the desired behavior I'd be glad to review the PR. |
Hi @xSAVIKx! Thank you for you feedback. I've reread the original issue and the desired behavior, and changed it accordingly in my PR. If you could review the PR that would be great! Thank you for your time! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vivjd overall LGTM. Would you be so kind to add a test case for this change in kafka-related test suite?
Hi @xSAVIKx, I changed the test cases to match the change. Could you please kindly review this again? Thank you in advance! |
Signed-off-by: vivjd <[email protected]>
Signed-off-by: Vivian <[email protected]> Signed-off-by: vivjd <[email protected]>
Signed-off-by: vivjd <[email protected]>
…tributes Signed-off-by: vivjd <[email protected]>
Sorry, my bad. I was pretty sure I did that when I was reviewing the PR |
Fixes #211
Changes
The
content-type
attribute will violate the attribute naming rules, so the attribute has been modified todatacontenttype
.One line description for the changelog
Converted
content-type
todatacontenttype
forcloudevents
.