Chiebot-Mirror/protobuf - protobuf - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
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
Paul Yang	5289ee0c21	Adopt ruby_package in ruby generated code. (#4627 ) * Adopt ruby_package in ruby generated code. * Add test for ruby_package	7 years ago
Paul Yang	9ccc3e536c	Adopt ruby_package in ruby generated code. (#4627 ) * Adopt ruby_package in ruby generated code. * Add test for ruby_package	7 years ago
Josh Haberman	6d92233e72	Added unit test for PascalCasing package names in Ruby.	8 years ago
Josh Haberman	4f19797baf	Ruby: generated foo.proto -> foo_pb.rb instead of foo.rb. This brings us more into line with other langauges, and makes it more obvious when we are requiring protobuf generated code.	8 years ago
Chris Fallin	3f3820d8f8	Two tests for Ruby code generator: - A golden-file test that ensures protoc produces known-valid output. - A Ruby test that loads that golden file and ensures it actually works with the extension. This split strategy allows us to test end-to-end without needing to integrate the Ruby gem build system and the protoc build system. This is desirable because we do not want a gem build/install to depend on building protoc, and we do not want building protoc to depend on building and testing the gem.	10 years ago