-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing documents on custom datetime sort order if you have many elements #1825
Comments
Hi and thank you for reporting! This is a known issue and we are looking into a fix 👍 |
I'm seeing the same issue. Weirdly, it only seems to happen in the dev server: my deployed version of Sanity Studio doesn't have this problem. |
I'm also seeing this issue (but on dev and prod), not just on sorts of datetime fields but also string fields (which we use a lot to sort by name or title). This is very confusing for editors since it seems like some documents are missing. It also makes for a bad experience when you are scrolling through the list, since halfway through (e.g. when you are already on the letter M) the list reorders and you jump to a different letter (e.g. letter C). This issue pretty much makes custom orderings unusable for document lists with more than a few dozen documents. Here's hoping a fix for this problem is found soon. 🤞 |
Was there any update on this? (or any pointers for where I might be able to start and try my hand at a fix)? |
Just encountered the same issue with ~150 records. Scrolling down then back up loads 10 missing posts at the top. Hoping this gets more traction. |
Any update on this one @vicbergquist? As noted in others comments this is quite a severe bug so it's quite concerning that the team hasn't been able to fix this in four months. |
@cbovis thanks for checking in on this, will look into it 😊 |
Any update on this one @vicbergquist ? |
Same issue with ~400 records. Any update? |
Same issue with ~2000 records. Any update? |
Hello here :) Any updates on this one ? |
Closing issue as this is fixed (again) on v2.30.1. |
I'm not getting the expected result out of a custom datetime sort order in the studio if I have so many documents that sanity will need to fetch more on scroll.
I have a schema with the following field:
and custom sort order according to https://www.sanity.io/docs/sort-orders:
Here are the first documents from the studio before scrolling:
After scrolling to the bottom of the list (no more documents to show) the first documents looks like this:
As you can see, after scrolling to the end of the list and up again the list have been populated with more documents (e.g. Jakobstrøm x Brakkesyke: Ē).
The second screenshot is the correct ordering and what I would expect to also get without scrolling.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The list should always look the same when using the same order.
Which versions of Sanity are you using?
What operating system are you using?
Which versions of Node.js / npm are you running?
The text was updated successfully, but these errors were encountered: