You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @j-palindrome -- thank you for reporting. I was able to see some of the same behavior that you're mentioning, and I agree that it's a bit unexpected and probably not the best user experience.
In my case, the issue was caused by two things --
Fields with a null or undefined datetime value get sorted first
The sort does not always privilege the draft document. So if I had a published document like:
The document would show up higher than it should have, based on what I was looking at.
In your case, do you have discrepancies between published and draft documents, or have undefined datetime fields?
Again, this is behavior that should be rectified and I am putting in a ticket for it, but I just wanted to confirm with you that we have accurately captured what's going on, and what we need to work on.
If you find a security vulnerability, do NOT open an issue. Email security@sanity.io instead.
Describe the bug
Sort order for date fields sorts in a seemingly random order.
To Reproduce
document
schema:Expected behavior
Descending sort order for dates in
YYYY-MM-DD
format.Screenshots
This collection is sorted like:
2022-11-01
2023-04-01
2021-11-01
2022-03-01
Which versions of Sanity are you using?
What operating system are you using?
MacOS Sonoma 14.2.1
Which versions of Node.js / npm are you running?
Run
npm -v && node -v
in the terminal and copy-paste the result here.The text was updated successfully, but these errors were encountered: