Repository navigation
Calling Set on nested JSON object returns invalid JSON after setting value #218
Description
Activity
- changed the title
[-]Calling Set on nest JSON object returns invalid JSON after setting value[/-][+]Calling Set on nested JSON object returns invalid JSON after setting value[/+]on Nov 29, 2020 yes，I found it, too
I got this issue today
I found this too, any update?
Reacted by Gokul KathirvelI get this issue too. How to deal with it?
I found a way to deal with it
Reacted by Neumoin Dmitry and Wonder- added a commit that references this issue
on Jul 28, 2026 Implemented in v1.4.0 — use
SetString(data, val, keys...)instead ofSet(data, []byte(val), keys...). SetString auto-quotes the value so the output is always valid JSON. See: https://github.com/buger/jsonparser/releases/tag/v1.4.0
If I call set on a deep nested JSON, the value after it returns misses the quotes required for a valid JSON
Input JSON:
{ "ipv4":{ "name":"testDependency", "source":{ "address":{ "group":"testDepenffdency", "ff":"aa" }, "port":{ "any":true } }, "uuid":"653e5654-b56b-47c1-b4e5-206acbb28f7a" } }code invoked:
Output:
{ "ipv4":{ "name":"testDependency", "source":{ "address":{ "group":KaranTest, "ff":"aa" }, "port":{ "any":true } }, "uuid":"653e5654-b56b-47c1-b4e5-206acbb28f7a" } }Here's an example of the problem: https://play.golang.org/p/YT3Ttz0Irib
However, if I pass :
It works as expected. Most of the time in programs we don't get strings like that. Is this by design? 😊 I'll have to wrap strings around " " to get around this issue.