tree 906efb59a27d289359040d97ea6591342a43f0ea
parent f02c9c72f5f0d63ce10da7b7393f58bc541e835a
author Charles OuGuo <shaldengeki@gmail.com> 1753044846 -0400
committer GitHub <noreply@github.com> 1753044846 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJofVd+CRC1aQ7uu5UhlAAA+48QAB5lVBQXEiBpVymZ4OJyyKei
 4GaPgJmh3Mmd3KRQzQTZdAIMxWsx+0DV9ZbKVSGTwLGzqfYB30/wioZY2KNXTMUq
 j6FHUODZ+noMXyZXiunD5urfNLf1e1C64fmOYXLMiNv64JmKwJST9nLh4WjTYL/B
 SoMDU8y7rVewdAhfIADBnV/RLvY0ctr5wL+Tmxsh6hQZbxl/uu+zR8byD3hAzFJr
 VhFUalLunB/x0tH9ZY2U79664onr2cE8M5NN9jNhKjEd3ZRukvmeKxCaUvHUVMMX
 eKqCY9gxTQdi0peSxY9kudnM7kWi19to6Xm0KO0LFq/R8yPhGHgeoJTtwGfeWxqR
 hurMxd2COzdwB0Ss5Igaxom7ltQJkMkzX4O37+1g4nt2rJFHSd9diZxF0MsKTqWu
 nZMmm8AAXV7Pu66FXS4n05Yrd3vCRXmHylWE01xYc4JPiY1gThcOdQ8AI3L0Foup
 QKP9TH4xWerJjSpF4ZfaZ4ZDc0dBGoBsvzN2IS0vENODzERQ86W+lVnzzzh+VyEI
 w3StrN9IxXkv9SPPXRWIxxVyZ614RvQ4J5hG+ownaw+tNr2y9GlsAFO8NmXz1Ks4
 xFPw43izHFTRow7FzXQtGQ01f52K9yZsr2WF1GpZD80HJ+R1UV0zEPhhGZHy16Fr
 bxreEjp2dzAnJhSoVynM
 =4VU/
 -----END PGP SIGNATURE-----
 

feat(gazelle): `python_proto_naming_convention` directive controls `py_proto_library` naming (#3093)

Closes https://github.com/bazel-contrib/rules_python/issues/3081.

This adds support in the Gazelle plugin for controlling how the
generated `py_proto_library` rules are named; support for these was
originally added in
https://github.com/bazel-contrib/rules_python/pull/3057. We do this via
a new Gazelle directive, `python_proto_naming_convention`, which is
similar to `python_library_naming_convention` and the like, except it
interpolates `$proto_name$`, which is the `proto_library` rule minus any
trailing `_proto`. We default to `$proto_name$_py_pb2`.

For instance, for a `proto_library` named `foo_proto`, the default value
would generate `foo_py_pb2`, aligning with [the convention stated in the
Bazel
docs.](https://bazel.build/reference/be/protocol-buffer#py_proto_library)