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
Just want to call out, while the fix works on the client it doesn't remediate a core issue on the server. Because this field (publishedAt) is typed as a string, sorting becomes wonky when you try to filter through db.find({ ... }).
Because it's a string, the filter really can't do much other than a string comparison (which inverts the logic now to use $gte vs $lte).
I came across this while trying to "future publish" (set date for future, not caring about sensitivity of the post, just that it didn't bubble up to UX "formally" until the date had passed).
Based on this discussion.
Lists are not currently being sorted by date.
The text was updated successfully, but these errors were encountered: