Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114697
To: internals@lists.php.net
Message-ID: <e1942470-dc68-0e20-3ccd-da420da74cb9@gmail.com>
Date: Thu, 3 Jun 2021 00:03:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: nl
Subject: json_encode indent parameter
From: tdegroot96@gmail.com (Timon de Groot)

It's not possible to tell json_encode what indentation level should be 
used when using
the JSON_PRETTY_PRINT option (2, 4, 8, etc). When generating JSON files 
which can be
used/read/edited by users, indentation starts to become a relevant topic.

- JavaScript has a function called JSON.stringify wich accepts the 
optional 'space' parameter
   - See 
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify 

- Python has a function called json.dump which accepts the optional 
'indent' parameter
   (which also controls pretty printing)
   - See https://docs.python.org/3/library/json.html#basic-usage

I would like to create an RFC draft to implement an 'indent' parameter.
Before I start a draft, I need to know if this is a good idea, so I 
start with a few questions.

1. What do you think of adding an 'indent' parameter?
2. How would that parameter work when the JSON_PRETTY_PRINT option is 
not passed?
3. What do you think of adding json_encode options instead, like
       JSON_PRETTY_PRINT_INDENT_2 and JSON_PRETTY_PRINT_INDENT_4?

Looking forward to you replies and feedback!

-- 

Kind regards,

Timon de Groot