À propos de Convertisseur JSON tolérant
Analyser les structures {clé=valeur} en JSON
This log-style format is not a formal grammar: nested objects use braces, lists use brackets, and values are unquoted, so a free-form message that contains its own commas and braces can look like additional keys. The converter keeps a value whole once it contains an '=', which preserves notification templates while still splitting ordinary keys.
Comment utiliser cet outil développeur
- Paste the {key=value, nested={...}, list=[...]} string, with or without the surrounding quotes from a log line.
- Convert it and review the JSON, paying attention to any free-form text values that carried commas or braces.
- Validate the JSON with the consumer's own parser before relying on the structure.
Confidentialité et traitement des données
Parsing runs locally in the browser. Redact webhook secrets, tokens, and personal identifiers from configuration samples before sharing the output.
Outils développeur associés
Questions fréquentes
Why does a message value keep commas and braces that look like other keys?
Once a scalar value contains an '=', it is treated as free-form text and absorbs later commas and braces up to the closing brace. This keeps notification templates like message=... success={SuccessCount}, fail={FailCount} intact instead of splitting them into separate keys.
Are numbers and booleans converted?
By default bare numbers and true/false/null become JSON numbers, booleans, and null. Values with leading zeros or too many digits to represent exactly stay strings, and you can turn coercion off to keep every value as a string.
Is this the same as JSON5 or a strict parser?
No. It targets the lossy, ambiguous toString() output of maps and objects, so it uses documented heuristics rather than a strict grammar. Verify the result when a value contains separators.