-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Moving protos out of protoc-gen-openapiv2/options directory to support Python #4407
Comments
Hi, thanks for your issue! I think this is very likely to break other users unfortunately. I'm sympathetic to the problem, but we can't break existing users. Are you able to do some other workaround perhaps? I'm not very familiar with bazel unfortunately. |
I am unfortunately running into the same issue, and it looks like a reasonable Bazel solution is to define a I want to note that the replacement of dashes with underscores is happening due to a Python This makes the output with underscores intended behavior and not specifically a Bazel issue, so I would expect other users of this repo using Python to also run into this issue, to some degree. When compiling protos manually, this is an easy fix because you can just go to the directory using underscores, but for more automated build systems this might be a problem. |
I ran the following bash scripts to generate the patch to rename the directory and apply it on my
|
🚀 Feature
Python codebase that is using Proto + Bazel would like to depend on those protos. Unfortunately having the protos being listed in a directory that has
-
causes issue withpy_proto_library
. Python proto compiler replaces "-" with "_" which means it resides in different directory (Ref).Is it possible if we move it to another directory without "-"? Thanks!
The text was updated successfully, but these errors were encountered: