kcl run --format toml returns wrong data

[diefans]

Bug Report

Using the --format toml option to render TOML instead of YAML returns a wrong result.
Seems like there is a custom/naive toml serializer in place...

1. Minimal reproduce step (Required)

kcl run --format toml /dev/stdin << EOF
schema Bar:

schema Foo:
    b: Bar
    a: str = "a"

Foo {
    b: Bar {}
}
EOF

2. What did you expect to see? (Required)

a = "a"

[b]

3. What did you see instead (Required)

[b]
a = "a"

4. What is your KCL components version? (Required)

kcl version is v0.10.8

[He1pa]

This is the order defined by schema attr. If you want to achieve what you want, just change the order of a and b.

schema Bar:

schema Foo:
    a: str = "a"
    b: Bar


Foo {
    b: Bar {}
}

I will temporarily close this issue. If you have any questions, please reopen it again.
By the way, as far as I know, the toml file is un-sort

[diefans]

The order of the KCL schema def should not matter here, but the order in the TOML matters, since at the moment (with this bug) kcl returns just wrong content by putting a into b but a is a sibling of b and not a child...

a TOML like

[b]
a = "a"

is the follwoing JSON

{
  "b": {
    "a": "a"
  }
}

while a TOML like

a = "a"
[b]

is the following JSON

{
  "a": "a",
  "b": {}
}

...so this issue is not fixed by just changing the order of KCL attributes, this would be unmaintainable if you consider subclassing and it would put the burden of sane serialization to the writer of KCL code.

[diefans]

@He1pa see https://toml.io/en/v1.0.0#table

Under that, and until the next header or EOF, are the key/values of that table.

[He1pa]

ok, i got you, I will fix it