Read/write nested data as flattened parameter name to and from toml file

[sverhoeven]

Refs #47

The haddock3 catalogs have not been updated. The different ways of supported flattening described at docs/tomlSchema.md can be tested by loading the kitchensink catalog and configuring node4.

Example worklow
workflow (16).zip

[netlify]

✔️ Deploy Preview for wonderful-noether-53a9e8 ready!

🔨 Explore the source changes: effed48

🔍 Inspect the deploy log: https://app.netlify.com/sites/wonderful-noether-53a9e8/deploys/6228c277d9a0150008d33c2c

😎 Browse the preview: https://deploy-preview-48--wonderful-noether-53a9e8.netlify.app

[Peter9192]

Haven't looked at the code yet, but from playing with the preview I noticed a couple of interesting things.

Point 1

With nested indexing the layout is a bit confusing. I click the first blue +, which effectively adds an empty nested array. As a user, the only visual feedback I get is the appearance of another blue + and a minus.

Since adding an empty array doesn't make much sense, does it make sense to automatically also create the first item in the nested array (and perhaps fill it with defaults or so, see #54)?

Point 2

The behavior when leaving boxes empty is also a bit tricky:

Note that 1_1 is skipped in the toml file, since it is apparently a default value, but the fact that the count then starts at 1_2 suggests that 1_1 is still significant. But what happens with the last one? It's also pruned from the toml file, but it can never be known that there would have been a 2_2 as well.

[Peter9192]

Looks very good, apart from my previous concern about the trailing empty array items I think it is good to go.

[Peter9192]

11, 22, and 33 are just example numbers, but due to their structure and correspondence to the params, it took me some time to realize they might as well be random other numbers. Perhaps we could consider making them a bit more arbitrary?

[sverhoeven]

I chose those number to easily map the indices to the values. Using arbitrary numbers would make it harder to investigate any errors.

[Peter9192]

But this is the documentation, not testing code or so

[sverhoeven]

Thanks for the review.

For point 1 the table widget in #53 and 2d matrix widget #56 will help.

For point 2 trailing items which are equal to defaults and absent in toml is something the app running the toml needs to deal with.