Sorting by reverse in org.hypercerts.claim.activity doesnt seem to properly sort by created at date. and instead seems to be a bit random
Type: bug Project: hypercerts
A governance repo for all things of the hypercollective
Reverse filter in data browser doesnt sort properly #11
open
opened by
kzoeps.com
kzoeps.com
(author)
Thanks for the detailed repro @kzoeps! We identified the root cause: the data browser's CollectionsTab sorts by rkey via the PDS reverse parameter, which only works for TID-keyed collections. For org.hypercerts.claim.activity and others with non-TID rkeys (UUIDs/hashes), the lexicographic rkey order has no temporal meaning — so records appear in random order regardless of the sort toggle.
Fix is tracked internally: adding client-side sorting by extracted timestamp (from rkey-as-TID or the record's createdAt field) as a fallback, similar to what the Hyperboard tab already does.
This should now be fixed! CollectionsTab was relying on the PDS server-side rkey ordering, which is lexicographic and meaningless for non-TID rkeys. We've added client-side sorting by extracted timestamp (TID decode → createdAt fallback) so records now appear in proper chronological order regardless of rkey format. The fix is committed and will be live after the next deploy. Let us know if it still looks off!
The client-side sorting fix is working. Found and patched a minor leftover: the initial-load sort comparator had a hardcoded true instead of the reversed state variable, so toggling sort direction on first load was silently ignored. Now properly respects the sort toggle in all code paths. Deployed in commit 116da35.
https://www.impactindexer.org/data?did=did%3Aplc%3A666wpj2xloq7d6n5xjizhmbb&tab=collections
with this if you check out the org.hypercert.claim.acitivyt. the latest record is actually in the middle no matter how you sort it