Using Split in YAML

[chiragsanghavi]

When I use split in YAML and add steps - the expression part of split is moved to the end "with" steps layered in between.
Is that expected?

- route:
    id: route-2386
    from:
      id: from-2734
      uri: file
      parameters:
        directoryName: C:\work\camel-demos\NDJSONtoGCP\in
      steps:
        - log:
            id: log-1911
            message: ${headers}
        - doTry:
            id: doTry-1693
            steps:
              - log:
                  id: log-1382
                  message: ${headers}
              - split:
                  id: split-2274
                  steps:
                    - log:
                        id: log-2323
                        message: ${headers}
                  expression:
                    tokenize:
                      token: \n
            doCatch:
              - id: doCatch-4690
                steps:
                  - log:
                      id: log-4042
                      message: ${body}
                exception:
                  - java.lang.NullPointerException
            doFinally:
              id: doFinally-3347
              steps: []

I would have expected it to do:

              - split:
                  id: split-2274
                  tokenize:
                    token: \n
                  steps:
                    - log:
                        id: log-2323
                        message: "${headers}"

[lhein]

Does it cause any problems for the correct execution?

[chiragsanghavi]

There is no issue with execution. runs flawlessly. when I run dumpRouteAsYaml it prints togather.

[lhein]

So it is more of a cosmetic enhancement you are asking for? If yes, then please go on and create an issue for it. Thank you.

[davsclaus]

the camel-catalog has an index that can be used as guiding how the tool should create and dump the output files.
https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/split.json

The YAML DSL schema does not have this information as its based on some json schema spec
https://github.com/apache/camel/blob/main/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json

So kaoto would need to take the information from the camel-catalog and then use that to order the output.

But from runtime execution it does not matter, but as humans that look and read the yaml output then steps should always come last.