Boost C++ Libraries: Ticket #9721: ptree write_json does not conform to JSON standard

status changed; resolution set

Sebastian Redl — Thu, 27 Feb 2014 15:02:09 GMT

status new → closed
resolution → invalid

ptree internally only has strings. put converts from the values you put in to strings, as get converts back. However, the tree itself only contains strings, and therefore so does the output JSON.

Making a ptree variant that preserves JSON types is a future plan, but far off.

anonymous — Sun, 22 May 2016 19:29:50 GMT

Yet no update after years..

anonymous — Wed, 01 Jun 2016 12:18:34 GMT

there should be some updates about this problem, or the boost json can only be used as reader not writer

anonymous — Mon, 06 Mar 2017 19:11:27 GMT

Still nothing???

anonymous — Thu, 23 Mar 2017 01:20:31 GMT

A conformant JSON writer should be in Boost since long ago. This ticket has been resolved as invalid, I can't believe it!

anonymous — Wed, 10 May 2017 23:40:34 GMT

rapidjson seems to do the job.

anonymous — Wed, 10 May 2017 23:40:36 GMT

rapidjson seems to do the job.

anonymous — Thu, 19 Oct 2017 20:05:51 GMT

No way this is invalid! Proper JSON parsing is absolutely necessary.

rnistuk@… — Mon, 30 Oct 2017 22:25:57 GMT

Here's my fix for numbers:

#include <string>
#include <boost/regex.hpp>
  std::string fix_json_numbers(const std::string &json_str)
    {
        boost::regex re("\\\"([0-9]+\\.{0,1}[0-9]*)\\\"");
        return  boost::regex_replace(json_str, re, "$1");
    }

And here's a unit test:

BOOST_AUTO_TEST_CASE(test_fix_json_str)
    {
        std::string json_str_in ="{\"cmd\":\"test\",\"data\":{\"integer\":\"283\",\"float\":\"34.433\"}";
        std::string json_str_accepted ="{\"cmd\":\"test\",\"data\":{\"integer\":283,\"float\":34.433}";
        std::string json_str_actual = fix_json_numbers(json_str_in);
        BOOST_CHECK_EQUAL(json_str_accepted, json_str_actual);
    }

NOTE: I've modified the unit test a bit to call the fix_json_numbers function directly, I have not compiled the unit test.

status changed; resolution deleted

anonymous — Thu, 16 Nov 2017 07:41:44 GMT

status closed → reopened
resolution invalid

This looks like a valid problem and still seen in 1.64. PLs look into this issue.

anonymous — Thu, 16 Nov 2017 07:43:13 GMT

Write value Str data = create_escapes(pt.template get_value<Str>()); stream << Ch('"') << data << Ch('"');

This might be the code to be examined.

anonymous — Wed, 29 Nov 2017 13:51:50 GMT

Yep, i just wanted to use it for with JSON, issue still exist in 1.65

anonymous — Fri, 29 Dec 2017 19:22:06 GMT

What a shame! This ticket is 4 years old!

anonymous — Tue, 09 Jan 2018 23:34:10 GMT

Ok, rapidjson it is.

anonymous — Thu, 01 Mar 2018 16:25:51 GMT

yup i was doing research today to pick a json parser and i stumbled upon this thing... indeed rapidjson it is!

version changed

anonymous — Tue, 22 May 2018 09:17:55 GMT

version Boost 1.55.0 → Boost 1.67.0

This is still an issue for 1.67. Odd that for such a trivial requirement, boost has a long-pending issue.

anonymous — Tue, 19 Jun 2018 15:34:54 GMT

This is huge shortcoming! This should at the very least be documented using a proper disclaimer in the JSON section...