third_party.pigweed.src/pw_snapshot
Ted Pudlik 8ed38666b8 pw_tokenizer: Proto migration stage 3/5
This fixes Python package name collisions in Bazel, fixing the tokenizer
Python package and unblocking a large body of other work (basically,
Bazel support for anything that depends on the tokenizer Python,
including pw_system console).

This is a breaking change: any .proto files including,

    import "pw_tokenizer/proto/options.proto";

must now instead,

    import "pw_tokenizer_proto/options.proto";

Fixing this in internal downstream projects is stage 2/5 (see associated
issue).

Ordinarily, this type of proto file migration would also break users of
generated code. However, `options.proto` only defines an enum intended
to be used as a proto field option, so the generated code is not used
directly.

Bug: b/322850978
Change-Id: Ib9aafcf23a3e0ac6f07ffcce9e05745163963adf
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/189696
Reviewed-by: Armando Montanez <amontanez@google.com>
2024-02-13 23:35:34 +00:00
..
images
public/pw_snapshot
pw_snapshot_protos pw_tokenizer: Proto migration stage 3/5 2024-02-13 23:35:34 +00:00
py pw_tokenizer: Proto migration stage 3/5 2024-02-13 23:35:34 +00:00
BUILD.bazel
BUILD.gn
CMakeLists.txt
cpp_compile_test.cc
design_discussion.rst
docs.rst
module_usage.rst
OWNERS
proto_format.rst
setup.rst
uuid_test.cc
uuid.cc