commit | 84c9eab47433c23db28ddb67e67d83590dc80b74 | [log] [tgz] |
---|---|---|
author | Johannes Henkel <johannes@chromium.org> | Tue Dec 11 21:28:16 2018 |
committer | Johannes Henkel <johannes@chromium.org> | Tue Dec 11 21:28:16 2018 |
tree | 7a542ccd9d13c63849f2a8e8ae752919139cf394 | |
parent | a168ca5b1d518a3f00e6e6eecb769b50fe325dc5 [diff] |
Add unittests for the JSON parser errors. Bugs found: - strtod doesn't reset errno (linux_dev_platform.cc modified to cope) - two dead code branches (token != ArrayEnd / token != ObjectEnd) so I removed the two error codes UNEXPECTED_ARRAY_END / UNEXPECTED_OBJECT_END - one misleading error code (invalid token for no input), so I introduced a new one. JSON_PARSER_NO_INPUT Change-Id: I8453d92ce4b838a9c8f9718f52d97cb367a6d70c
This package contains code generators and templates for the Chromium inspector protocol.
The canonical location of this package is at https://chromium.googlesource.com/deps/inspector_protocol/
In the Chromium tree, it's rolled into https://cs.chromium.org/chromium/src/third_party/inspector_protocol/
In the V8 tree, it's rolled into https://cs.chromium.org/chromium/src/v8/third_party/inspector_protocol/
See also Contributing to Chrome Devtools Protocol.
We‘re working on enabling standalone builds for parts of this package for testing and development, please feel free to ignore this for now. But, if you’re familiar with Chromium's development process and have the depot_tools installed, you may use these commands to fetch the package (and dependencies) and build and run the tests:
fetch inspector_protocol cd src gn gen out/Release ninja -C out/Release json_parser_test out/Release/json_parser_test