diff options
author | Adam Cozzette <acozzette@google.com> | 2016-09-27 15:36:41 -0700 |
---|---|---|
committer | Bo Yang <teboring@google.com> | 2016-10-10 11:44:21 -0700 |
commit | 4a4a1627c158d976ee80f278024a49ced8b12712 (patch) | |
tree | 7f619a542f6e83f251284b7561a789672df94b11 /js/message_test.js | |
parent | 0bf5482712e849f67d7fe98217608f95ba60c776 (diff) | |
download | protobuf-4a4a1627c158d976ee80f278024a49ced8b12712.tar.gz protobuf-4a4a1627c158d976ee80f278024a49ced8b12712.tar.bz2 protobuf-4a4a1627c158d976ee80f278024a49ced8b12712.zip |
Fixed references to foreign nested messages with CommonJS-style imports
A bug was causing generated JSPB code with CommonJS-style imports to
refer incorrectly to nested messages from other .proto files. The
generated code would have things like "test_pb.InnerMessage" instead of
"test_pb.OuterMessage.InnerMessage". This commit fixes the problem by
correctly taking into account any message nesting.
Diffstat (limited to 'js/message_test.js')
-rw-r--r-- | js/message_test.js | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/js/message_test.js b/js/message_test.js index 97c594c8..b0a0a72e 100644 --- a/js/message_test.js +++ b/js/message_test.js @@ -1040,4 +1040,18 @@ describe('Message test suite', function() { assertNan(message.getDefaultDoubleField()); }); + // Verify that we can successfully use a field referring to a nested message + // from a different .proto file. + it('testForeignNestedMessage', function() { + var msg = new proto.jspb.test.ForeignNestedFieldMessage(); + var nested = new proto.jspb.test.Deeply.Nested.Message(); + nested.setCount(5); + msg.setDeeplyNestedMessage(nested); + + // After a serialization-deserialization round trip we should get back the + // same data we started with. + var serialized = msg.serializeBinary(); + var deserialized = proto.jspb.test.ForeignNestedFieldMessage.deserializeBinary(serialized); + assertEquals(5, deserialized.getDeeplyNestedMessage().getCount()); + }); }); |