From 88e9dd9fc94b39e69b639d2891c4155f071679d8 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Thu, 8 Oct 2026 12:27:01 +0200 Subject: [PATCH] Say why null stays JSON in the padded-JSON decision --- docs/decisions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/decisions.md b/docs/decisions.md index 2072c37..b77a54a 100644 --- a/docs/decisions.md +++ b/docs/decisions.md @@ -118,9 +118,9 @@ until item 129: it reads a path, and only the data is absent. Padding is where the two readings disagree: a format string renders it, JSON drops it. A template that parses as a JSON object, array, string or `null` is its JSON, so its padding -is dropped, as `encoding/json` drops it. A bare number or boolean gains nothing from the -JSON reading, so it is a format string, and `echo 42` prints its newline as `echo x` does -(goal 5.1). +is dropped, as `encoding/json` drops it. `null` stays JSON, since it is how a template +renders nothing. A bare number or boolean gains nothing from the JSON reading, so it is a +format string, and `echo 42` prints its newline as `echo x` does (goal 5.1). ## A JSON string stays a template even where its bare text renders alike