open-source-parsers / open-source-parsers/jsoncpp

There are some errors when using reader. parse()

Open
#1,481 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
8.9k
Forks
2.7k
Avg merge
31m
Merged PRs (30d)
1

Description

        string resPost0;
        auto res3 = curl_post_req(url_post0, paramsLogin0, resPost0);
        if (res3 == CURLE_OK)
        {
            cout << resPost0 << endl;
            Json::Reader reader;
            Json::Value json_object;
            Json::Value json_repose;
            string json_document = "{\"status\": true, \"errorcode\": 0, \"response\": {\"operation\": 1}, \"remarks\": null}";
            if (!reader.parse(resPost0, json_object))
                return 0;
            std::cout << json_object << std::endl;
        }

[result]

"{\"status\": true, \"errorcode\": 0, \"response\": {\"operation\": 1}, \"remarks\": null}"
"{\"status\": true, \"errorcode\": 0, \"response\": {\"operation\": 1}, \"remarks\": null}"

[information]
If I were using curl_ post_ The string obtained by req() will result in the same input and output strings. If I use JSON_ Document, then normal data can be obtained.
[version]
The version I am using is 0.10.7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository file or test. Start by reproducing the reader.parse(resPost0, json_object) call with the shown curl response and compare it with the JSON_Document path; determine the expected input and failure behavior before identifying a focused fix or regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend-api-design
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.