-
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
Introduce protobuf formatter #933
Conversation
2892b47
to
353fd7c
Compare
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
} | ||
|
||
extend Foo { | ||
option (my_option) = "my_value"; |
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.
Removed this because extending with options seems to be invalid proto.
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.
First pass, some notes here and some directly between me and author.
70dc909
to
8833da7
Compare
41ece6c
to
6a5731d
Compare
Protobuf formatter is written in go and based on the buf formatter. It is installed as Extension and introduces go as dependency. If enabled it will run on top and independent of normalization.
6a5731d
to
6d954e6
Compare
About this change - What it does
This PR adds an optional formatter for protobuf schemas.
Protobuf formatter is written in go and based on the buf formatter. It is installed as Extension and introduces go as dependency. If enabled it will run on top and independent of normalization.
Why this way
Karapace protobuf normalization is not feature complete which can lead to issues if e.g. different Kafka producers are used.
This is a short term fix for those issues.
In the future either normalization will have to be improved or moved entirely to go/protocompile/buf.