-
Notifications
You must be signed in to change notification settings - Fork 3
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
Question on forked dependencies #38
Comments
The forks are required, because:
|
@rvolosatovs Do you think these protoc-gen-star will actually ever be merged? One was closed but I haven't seen if there was a replacement PR merged or anything |
Not sure, but so far it does not look too promising. |
There are 2 forked dependencies in use: https://github.com/TheThingsIndustries/protoc-gen-validate and https://github.com/TheThingsIndustries/protoc-gen-star
This causes troubles becase all consumers of
protoc-gen-fieldmask
module also have to addreplace
directives to their go.mod files, e.g.Is there any strong reason to keep using these forks? Are this forks long-running i.e. the updates will never land into upstream? If so, maybe we should rework them so only the required functionality is kept, and other is discarded, to break upstream dependency.
As another option, would it make sense to move required functionality from https://github.com/TheThingsIndustries/protoc-gen-validate directly to this repository and again remove the dependency? E.g. as
protoc-gen-fieldmask
supports only Go we don't need upstream features for Java and Python. Probably we could just copy required code here so it's all in one place.WDYT?
Sorry if my questions make no sense, as I may have incorrect assumptions about these forks.
The text was updated successfully, but these errors were encountered: