protobuf

Commit Graph

Author	SHA1	Message	Date
Joshua Haberman	fa338b70a6	Added UPB_ASSERT() that helps avoid unused var warnings. * Added UPB_ASSERT() that helps avoid unused var warnings. * Addressed PR comments. * Fixed assert in the JIT.	9 years ago
Joshua Haberman	e6fa3f9d86	Changed schema for JSON test to be defined in a .proto file. (#54 ) * Changed schema for JSON test to be defined in a .proto file. Before we had lots of code to build these schemas manually, but this was verbose and made it difficult to add to the schema easily. Now we can just write a .proto file and adding fields is easy. To avoid making the tests depend on upbc (and thus Lua) we check in the generated schema. * Made protobuf-compiler a dependency of "make genfiles." * For genfiles download recent protoc that can handle proto3. * Only use new protoc for genfiles.	9 years ago
Joshua Haberman	89197b9358	JSON parser: always accept both name variants, flag controls which we generate. * JSON parser: always accept both name variants, flag controls which we generate. My previous commit was based on wrong information about the proto3 JSON spec. It turns out we need to accept both field name formats all the time, and a runtime flag should control which we generate. * Documented the preserve_proto_fieldnames option. * Fix bugs in PR.	9 years ago
Josh Haberman	f9afc3e55b	Changed JSON parser/printer to correctly camelCase names.	9 years ago
Josh Haberman	146a9c22ef	Added lots of decoder tests and fixed lots of bugs.	9 years ago
Josh Haberman	abcb6428ad	Changed parser semantics around skipping. Prior to this change: parse(buf, len) -> len + N ...would indicate that the next N bytes of the input are not needed, and would advance the decoding position by this much. After this change: parse(buf, len) -> len + N parse(NULL, N) -> N ...can be used to achieve the same thing. But skipping the N bytes is not explicitly performed by the user. A user that doesn't want/need to skip can just say: parsed = parse(buf, len); if (parsed < len) { // Handle suspend, advance stream by "parsed". } else { // Stream was advanced by "len" (even if parsed > len). } Updated unit tests to test this new behavior, and refactored test utility code a bit to support it.	10 years ago
Josh Haberman	49dab06e03	Brought into compliance with Google open-source policies. - removed myself from Author headers in source files. - removed copyright notices from source file headers. - added CONTRIBUTING.md	10 years ago
Josh Haberman	3bd691a497	Google-internal development.	10 years ago
Martin Maly	508c39ee13	Resolve compilation errors if compiled with more stringent semantic checks. Adding Travis test to build with strict warnings. Fixing a warning in a test which used signed/unsigned integer comparison.	10 years ago
Chris Fallin	fb58504569	Support maps in JSON parsing and serialization. This is a sync of our internal developing of JSON parsing and serialization. It implements native understanding of MapEntry submessages, so that map fields with (key, value) pairs are serialized as JSON maps (objects) natively rather than as arrays of objects with 'key' and 'value' fields. The parser also now understands how to emit handler calls corresponding to MapEntry objects when processing a map field. This sync also picks up a bugfix in `table.c` to handle an alloc-failed case.	10 years ago
Josh Haberman	87fc2c516b	Changes from Google-internal development. * JSON parser expanded to handle split buffers. * bugfix to the protobuf decoder.	10 years ago
Chris Fallin	8f8113b4ff	JSON test, symbolic enum names in JSON, and a few improvements. - Added a JSON test that round-trips (parses then re-serializes) several test messages, ensuring that the re-serialized form matches the original exactly. - Added support for printing and parsing symbolic enum names (rather than integer values) in JSON. - Updated JSON printer to properly handle string fields that come in multiple pieces. ('bytes' fields still do not support this, and this work is more challenging because it requires making the base64 encoder resumable. Base64 encoding is not separable at an input-byte granularity, unlike string escaping.) - Fixed a < vs. <= bug in UTF-8 encoding generation (oops).	10 years ago

13 Commits (cbc2d7af561e149e7c445e63a485793e2669b89c)