Extending frontMatter.content.sorting #497

Open
opened 2026-10-05 02:50:23 +02:00 by adam · 0 comments
Owner

I have configured SORTING like this:

  "frontMatter.content.sorting": [
    {
      "title": "Updated (asc)",
      "name": "updated",
      "order": "asc",
      "type": "date"
    },
    {
      "title": "Updated (desc)",
      "name": "updated",
      "order": "desc",
      "type": "date"
    }
  ]

... but only the posts that have also been updated have the field UPDATED in the front matter. Therefore it will be NULL for all un-updated posts and the sorting after those who have been updated is ?? random ??.

It would be cool, if it is possible to define a SUBSTITUTE field ... in my case it would be "date".

I have configured SORTING like this: ``` "frontMatter.content.sorting": [ { "title": "Updated (asc)", "name": "updated", "order": "asc", "type": "date" }, { "title": "Updated (desc)", "name": "updated", "order": "desc", "type": "date" } ] ``` ... but only the posts that have also been updated have the field UPDATED in the front matter. Therefore it will be NULL for all un-updated posts and the sorting after those who have been updated is ?? random ??. It would be cool, if it is possible to define a SUBSTITUTE field ... in my case it would be "date". <!-- github-sync-id:1862784280 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#497