Skip to content

First level keys not sorted by default with sort yaml command #193

Description

@UyttenhoveSimon

Hello,

First thanks for your extension.
Second, apologies if such thing exists but I could not find a similar issue opened/closed or anything in the documentation.

Issue:

nq:
  auth:
    org-organization-uuids:
      '7680': toto
    org-sso-ids:
      '7680': tata
  deployments:
    dashboard:
      api:
        key: 7df5f
        url: ${url}
      data:
        environment: UAT
        manifest-file: file:/data/workdir/manifest.json
      enabled: true
      
environment:
  name: Test

When using "sort yaml" command, the nq key and its child nodes are not placed below environment key.
If I use "Custom sort 1" it does the sorting as expected.

Is this behavior expected ?

Thanks in advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions