Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | JS: ensure that extension values are serialized even if they're falsy | 2017-03-06 | |
| | | | | | | | | There was a bug where for JavaScript we would only serialize an extension value if it evaluated as truthy, which meant that values like 0 would get silently dropped (even in proto2, where field presence is significant). This fixes issue #2605, and takes care of the output of toObject() in addition to the binary format. | ||
* | Fixed remaining JSPB test failures | 2016-11-21 | |
| | |||
* | Integrated internal changes from Google | 2016-11-17 | |
| | |||
* | Integrate internal changes | 2016-10-10 | |
| | |||
* | Integrate google internal changes. | 2016-03-30 | |
| | |||
* | Fix CommonJS relative require generation, and test it | 2016-02-24 | |
| | |||
* | Fixed nested message scopes for CommonJS. | 2016-02-18 | |
| | |||
* | CommonJS tests are now passing. | 2016-02-18 | |
| | |||
* | Enable JavaScript tests for binary parse/serialize. | 2016-02-02 | |
| | | | | | | | | These should have been included in the first match but I overlooked them. This involved deleting some of the code that tests Google-internal-only features. | ||
* | Down-integrate from internal code base. | 2015-12-11 | |