-
Notifications
You must be signed in to change notification settings - Fork 583
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
Remove gogo support #340
Remove gogo support #340
Conversation
Signed-off-by: michael.wozniak <[email protected]>
Signed-off-by: michael.wozniak <[email protected]>
Signed-off-by: michael.wozniak <[email protected]>
dir Signed-off-by: michael.wozniak <[email protected]>
Signed-off-by: michael.wozniak <[email protected]>
Signed-off-by: michael.wozniak <[email protected]>
I'm fine dropping gogo since I found it difficult to maintain personally. I am not aware of other users of protoc-gen-validate gogo feature. |
SGTM. @wozz can you merge master? |
Sorry, looks like merging #343 introduced a few more conflicts. Once more, please! |
No, please keep them separate. It looks like there are still some |
Thanks, I had the order reversed in my head. I'll go ahead and take a look over there then |
Signed-off-by: michael.wozniak <[email protected]>
Signed-off-by: michael.wozniak <[email protected]>
Thanks! |
This reverts commit c7c8be4.
Splitting up #338 into smaller changes. This change removes support for gogo.
The main reason to drop support is so that protoc-gen-validate can be updated to use the new protobuf API, which gogo does not support. Additionally, it seems up in the air if gogo will continue to be maintained: gogo/protobuf#691
If support is later added for gogo and maintenance picks back up, gogo support can be added back to protoc-gen-validate.
These changes are built on top of #339