apt/test/libapt/json_test.cc, branch 2.9.2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.22024-04-20T12:15:47Zbuild: test: Silence warnings in GTest code2024-04-20T12:15:47ZJulian Andres Klodejulian.klode@canonical.com2024-04-20T12:09:37Zurn:sha1:4e9a9dbf9bd52d38ab5818f3eb32c8189fd25671
GTest has a lot of broken things with signed vs unsigned,
and double integer promotions, let's silence them.
json: Encode NULL strings as null2021-04-23T10:25:40ZJulian Andres Klodejulian.klode@canonical.com2021-04-21T10:21:41Zurn:sha1:b5211b9b213273c642a790ae3c3f3bbe1a4cf51e
This is the only nullable thing we have here.
json: Actually pop states2021-04-23T10:25:40ZJulian Andres Klodejulian.klode@canonical.com2021-04-21T10:17:55Zurn:sha1:09e3c0c855e339216784a1d43715c3ae2d79ec23
The JSON encoder only looked at the top state, but did not
pop it, so if we nested objects, we got stuck in whatever
the last state we pushed aside was, so in our example, we
wrongly get a comma inserted _after_ key "b":
{"a":[{}],
"b":,[{}]
}
json: Escape strings using \u escape sequences, add test2021-04-23T10:25:40ZJulian Andres Klodejulian.klode@canonical.com2021-04-21T09:31:46Zurn:sha1:57b727af4e1eea4ea118ca5e5028fa7ce86fb538
This allows us to correctly encode strings containing quotation
marks, escape characters and control characters.
The test case is a bit nasty because it embeds private-cachefile.cc
for linkage reasons.