René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add client-side sorting optimization for live query subscriptions","articleBody":"## Summary\nImplement client-side sorting mechanism to prevent unnecessary server refetches when entities are updated in live query subscriptions.\n\n## Background\nWhen using `watch()` subscriptions without `limit` or `skip` clauses, the client can optimize updates by:\n1. Updating the modified entity in the local list\n2. Re-sorting the list client-side\n\nThis avoids the \"sliding window\" problem and reduces server load.\n\n## Proposed Implementation\n\nWhen a snapshot update is received:\n1. If the subscription has no `limit`/`skip` options:\n   - For `modified`: Update the entity in place and re-sort\n   - For `added`: Insert the entity and re-sort\n   - For `removed`: Remove the entity from the list\n2. If the subscription has `limit`/`skip`:\n   - Request a full refetch from the server (sliding window case)\n\n## Technical Details\n\n### Sort Parsing\nThe SDK already uses `--` prefix for descending sort (e.g., `--price` for descending by price). Implement a sort comparator that:\n- Parses the sort string\n- Handles ascending/descending\n- Supports nested field paths\n\n### Files to modify:\n- `src/modules/entities.ts` - Add sorting logic in watch handler\n- `src/utils/common.ts` - Add sort utility function\n\n## Considerations\n- Document that `limit`/`skip` subscriptions will trigger full refetches\n- Consider recommending filter-only subscriptions in docs\n- Maintain consistency with server-side sort behavior\n\n## Related\n- Depends on #83 (watch() method implementation)","author":{"url":"https://github.com/guyofeck","@type":"Person","name":"guyofeck"},"datePublished":"2026-01-22T19:48:51.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/84/javascript-sdk/issues/84"}