JSON indentation option in decode method

[johannschopplich]

i think it would be nice if we add json indentation option in this function

Originally posted by @bpradana in #6 (comment)

[kumarguddu609]

@johannschopplich Thanks for opening this! Could you clarify what kind of indentation option you’re envisioning for the decode method?

Do you mean allowing a parameter like indent=2 (similar to json.dumps) to pretty-print the decoded output, or are you referring to something else in the parsing process?

[albertoZurini]

I'm going to be handling this issue.

@IGaneshD, your code has some problems and it can't be added to the main repo. If you want to have a call together we can integrate the changes in a new PR :)

[albertoZurini]

Hey @jreakin, I was having a look at your PR.
Disclaimer: I'm currently not an official maintainer of this project.

I wanted to ask you if you think the tests that you put are enough. I was having a look at the SPEC repository and, in the tests section, they are performing way more tests. What do you think? Do you think further tests should be added?

[jreakin]

Hey @jreakin, I was having a look at your PR. Disclaimer: I'm currently not an official maintainer of this project.

I wanted to ask you if you think the tests that you put are enough. I was having a look at the SPEC repository and, in the tests section, they are performing way more tests. What do you think? Do you think further tests should be added?

Thank you for the constructive feedback, @albertoZurini! The latest commit removes the hardcoded tests entirely and replaces them with spec-based parametrized tests using the official TOON spec fixtures. All 439 spec fixture tests are passing along with the 19 new json_indent tests.

The json_indent feature is now validated across 160+ spec test cases. When the spec changes, the tests automatically evolve with it.