Skip to content
Snippets Groups Projects
  1. May 09, 2024
  2. May 08, 2024
  3. May 07, 2024
  4. May 06, 2024
  5. May 04, 2024
  6. May 03, 2024
  7. May 02, 2024
  8. May 01, 2024
  9. Apr 30, 2024
  10. Apr 24, 2024
  11. Apr 23, 2024
  12. Apr 21, 2024
  13. Apr 20, 2024
  14. Apr 19, 2024
    • Latte macchiato's avatar
      Rework cache clearing to be fault tolerant · dd3d562a
      Latte macchiato authored
      dd3d562a
    • dakkar's avatar
      make eslint happy · fa60c1d4
      dakkar authored
      also add some types to `chiptune2.ts`
      fa60c1d4
    • dakkar's avatar
      rework pagination - fixes #491 · dbfafe25
      dakkar authored
      previously, when adding items either at the beginnig (e.g. new notes
      coming in while we're not looking at the top of the timeline) or a the
      end (e.g. more items arriving from a background fetch) of a paginated
      view, the resulting list got truncated to `displayLimit`, potentially
      throwing data away and causing a new fetch.
      
      This, coupled with the async nature of scrolling & fetching, could
      cause weird results.
      
      Also, `offset` was always incremented by the size of the fetched
      results, even if not all of them were displayed, meant that it was
      possible for offset-based pagination to drop items.
      
      Finally, the "queue" of new items (usually, new notes) also got
      truncated to `displayLimit`, which again could drop items (this effect
      was usually masked by the first point: when scrolling to the top of
      the timeline, if the queue's length was equal to `displayLimit`, those
      notes displaced any existing ones, `unshiftItems` set
      `more.value=true`, you got scrolled to the top, and notes were fetched
      again, so you lost your position but at least all notes got shown,
      eventually)
      dbfafe25
  15. Apr 11, 2024
Loading