... 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 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I have configured SORTING like this:
... 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".