-
Notifications
You must be signed in to change notification settings - Fork 71
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
fix: return "messages" instead "incompatibilities" from compatibility API #975
Merged
keejon
merged 1 commit into
main
from
jjaakola-aiven-correct-schema-compatibility-response-field
Oct 16, 2024
Merged
fix: return "messages" instead "incompatibilities" from compatibility API #975
keejon
merged 1 commit into
main
from
jjaakola-aiven-correct-schema-compatibility-response-field
Oct 16, 2024
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
keejon
reviewed
Oct 16, 2024
keejon
reviewed
Oct 16, 2024
jjaakola-aiven
force-pushed
the
jjaakola-aiven-correct-schema-compatibility-response-field
branch
from
October 16, 2024 10:02
951780e
to
761faac
Compare
LGTM, thanks for fixing this |
keejon
previously approved these changes
Oct 16, 2024
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.
LGTM 👍
jjaakola-aiven
force-pushed
the
jjaakola-aiven-correct-schema-compatibility-response-field
branch
from
October 16, 2024 10:54
761faac
to
bdc93da
Compare
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
… API For Confluent Schema Registry client compatibility the response field is changed from "incompatibilities: str" to "messages: list[str]".
jjaakola-aiven
force-pushed
the
jjaakola-aiven-correct-schema-compatibility-response-field
branch
from
October 16, 2024 12:05
bdc93da
to
a0c664d
Compare
Claudenw
reviewed
Oct 16, 2024
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.
LGTM
keejon
approved these changes
Oct 16, 2024
keejon
deleted the
jjaakola-aiven-correct-schema-compatibility-response-field
branch
October 16, 2024 16:53
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.
For Confluent Schema Registry client compatibility the response field is changed from "incompatibilities: str" to "messages: list[str]".
About this change - What it does
References: #xxxxx
Why this way