protobuf

Commit Graph

Author	SHA1	Message	Date
Protobuf Team Bot	1f472f1db3	Remove proto_best_practices from Rust test files in OSS PiperOrigin-RevId: 676434510	3 months ago
Alyssa Haroldsen	1eab5a0237	Generate `pub use` for imported enums PiperOrigin-RevId: 596762218	11 months ago
Joshua Haberman	177092cd8c	Shorten our license headers into an abbreviated form that references LICENSE instead of including it in full. PiperOrigin-RevId: 563888978	1 year ago
Marcel Hlopko	3ced818640	Add support for proto_library with more than one srcs If a proto_library has more than one srcs, we designate the first one as the primary (that file will be passed to rustc as the crate root). All other files will represent (internal) submodules of the crate. In general, Rust users won't see which .proto file a message came from, they will only see a crate corresponding to the entire proto_library, and in it public submodules for all `package` statements in all .proto files in the proto_library sources. Therefore in this CL we reexport all messages from non primary sources into their corresponding public modules (= packages declared in their owning .proto files). Besides the common case this CL also handles .proto files without package statement, and a subset of behaviors needed for public import functionality. PiperOrigin-RevId: 549543321	1 year ago
Hong Shin	4f20efbb78	Internal Change PiperOrigin-RevId: 546867607	1 year ago
Marcel Hlopko	a1ba8d238a	Generate bindings under the correct package. Before this CL all messages were generated in the top-level crate module. With this change we generate messages under the module specified by the package declaration in the .proto file. Dots are interpreted as submodule separator in consistency with how C++ namespaces are handled. Note that name of the proto_library target still remains to be used as the crate name. This CL only adds crate submodules dependeing on the specified package. PiperOrigin-RevId: 524235162	2 years ago
Marcel Hlopko	083830d849	Update copyright year PiperOrigin-RevId: 521800787	2 years ago
Marcel Hlopko	26af540a7a	Add support for proto dependencies to rust_proto_library PiperOrigin-RevId: 514719215	2 years ago
Mike Kruskal	b393dace83	Reverting bad merges due to OSS changes since last sync	2 years ago
zhangskz	740c4b082d	Update ruby_generator.cc to allow proto2 imports in proto3 (#9003 ) * Update ruby_generator.cc to allow proto2 imports in proto3, with updated unit tests * Update Makefile.am with new ruby_generated_code_proto2_import.proto * Fix ruby_generator unit test to use temporary test directory for imported protos * Add test for imported proto2 to ruby/tests * Fix proto_path, restore to ../src/protoc, and fix/cleanup unit test. * Rename Proto2TestMessage to TestImportedMessage for consistency, for ruby compiler tests	3 years ago
listonjesse	2ae7cf0e03	Auxillary -> Auxiliary	5 years ago
Harshit Chopra	d0535cc09e	Adds support for proto2 syntax for Ruby gem. This change only adds basic proto2 support without advanced features like extensions, custom options, maps, etc. The protoc binary now generates ruby code for proto2 syntax. However, for now, it is restricted to proto2 files without advanced features like extensions, in which case it still errors out. This change also modifies the DSL to add proto messages to the DescriptorPool. There is a new DSL Builder#add_file to create a new FileDescriptor. With this, the generated ruby DSL looks something like: Google::Protobuf::DescriptorPool.generated_pool.build do add_file "test.proto" do add_message "foo" do optional :val, :int32, 1 end end end	6 years ago

4 Commits (7a182690722f15c665cf874c2e25a11687f1e721)