-
Notifications
You must be signed in to change notification settings - Fork 581
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
ensure the imports are used
is broken
#585
Comments
ensure the imports are used
is broken
Help please |
We're running into this issue as well. Are there any updates on this? Thanks! |
Same here. I get: var (
// ...
_ = ccsds.DataType(0)
_ = manoeuvre.DataType(0)
) However, only |
Hey @rodaine not sure if you are the right person to look at this but this bug is pretty severe. The generated go code is unusable. I think the culprit is the change in the template (go/file.go) it would seem to me that the index on the second lookup is fixed and that is why the combo of pkg/path is broken and you always get the same enum name regardless... I honestly don't understand why the change was made in the first place (like I don't get what was the case) but as of now this is broken. I can try a couple of combinations and see if I can come up with a fix but if you can see the fix and can do it faster than I can it would be great to have this in. |
I would also be interested in an update on this. It makes the validator generation unusable for some of our proto files. |
Signed-off-by: Eduardo Solis <[email protected]>
@rodaine @keith @rmichela sorry for just randomly pinging you on this issue!! It honestly is pretty bad since the code that gets generated is unusable... I sent a PR last night but then I just realized there are a couple others trying to address it!! This seems to be the list: #586 Is there any way to get any of these in and close the issue for good? |
I hate to be the bearer of bad news, but per #616 PGV is effectively unmaintained. |
Signed-off-by: Elliot Jackson <[email protected]>
Hey @elliotmjackson thank you so much for starting work on this one!! I see that the PRs are getting closed, do you happen to have an ETA on when this will be fixed? |
yeah working on it now, shouldn't be too long at all - the fix has existed on various forks in the wild for a long time so it's looking fairly straight forward. In saying that, I'm still finding my feet maintaining the project so thanks in advance for you continued patience. |
@elliotmjackson thank you!!! Happy to help if I can! |
Just to let you know that we included another fix to solve an issue with enums that belong to the same proto package name but have a different go packages defined on them. This happens in those packages like google.type. References:
Fix: |
Signed-off-by: Eduardo Solis <[email protected]> Signed-off-by: Eduardo Solis <[email protected]> Co-authored-by: Elliot Jackson <[email protected]>
We have a proto with this message
After upgrading protoc-gen-validate we are getting this error
When I checked the generated code
The issue
types.BankEnum_Bank(0)
should betypes.Language(0)
The text was updated successfully, but these errors were encountered: