[Bug?] The same incorrect sorting syntax doesn't raise syntax error when specified at folder level

[SebastianMC]

Compare these two examples of invalid syntax:

---
sorting-spec: |
  target-folder: dummy
    > modified, created
---

---
sorting-spec: |
  target-folder: dummy
  > modified, created
---

The latter doesn't generate syntax error.
Investigate if the secondary sorting in that case is ignored, parsed incorrectly or maybe parsed with some default assumption of the secondary order?

[SebastianMC]

Summary

In a nutshell: the sorting direction specification (e.g. <, >, asc:, desc:, order-asc:, ...) is required only at the beginning of a line, to recognize the line as a sorting specification - no direction specification at the beginning of a line results in treating the line as a regular group definition to match files and/or folder.

For the same reason, the secondary sorting specification doesn't need the sorting direction prefix - if the order prefix is not provided, the ascending direction is assumed.

Relevant examples

Syntax error because a nested sorting specification requires prior group definition

Note the additional indentation in > modified, created

---
sorting-spec: |
  target-folder: dummy
    > modified, created
---

Perfectly valid two-level sorting specification for the folder

Note no additional indentation in > modified, created
The resulting sorting definition is:

• primary order is descending modified
• secondary order is ascending created

---
sorting-spec: |
  target-folder: dummy
  > modified, created
---