| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
It's pointless to add the '-test' suffix to files under the tests/ directory.
|
| |
|
|
|
|
| |
Since we load up a test file from a directory, we should be using a
path - otherwise this will break out-of-tree builds, e.g. when doing
a distcheck.
|
| | |
|
| |
|
|
|
|
| |
We identify a missing ':' separator between an object member name and
its value, so it would be a good thing to actually have an error code
for that.
|
| |
|
|
|
|
|
|
|
| |
The JsonScanner error reporting mechanism, which is basically
GScanner's, sucks beyond belief. In order to report an error code we
need to store it inside the JsonParser private structure and then use it
when creating the GError inside the error handler.
This, frankly, is quite stupid.
|
| | |
|
| |
|
|
|
| |
The nested object test should use something that's really complex: an
object with a nested array and nested object definitions.
|
| | |
|
| |
|
|
| |
Verify that invalid JSON will trigger a parser error.
|
|
|
Use the json-glib/tests directory for testing the data structures of
JSON-GLib: node, object, array, parser and generator.
The tests/ directory should be used for complex test cases, like the
GObject and GBoxed integration - but the goal is to remove the top-level
tests/ directory altogether, since the conformance test suite should be
built along the json-glib/ directory.
|
