Skip to content

Use timestamp-based reportAction pagination #14235

Closed

Description

@roryabraham

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Problem

We recently finished building the back-end infrastructure for timestamp-based pagination, but we are not yet using it in the front-end.

Solution

Let's button this up and use timestamp-based pagination in the front-end.

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01005257f49e677972
  • Upwork Job ID: 1613348894782074880
  • Last Price Increase: 2023-01-12

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    NewFeatureSomething to build that is a new item.
    on Jan 12, 2023
  2. locked and limited conversation to collaborators on Jan 12, 2023
  3. self-assigned this
    on Jan 12, 2023
  4. unlocked this conversation on Jan 12, 2023
  5. melvin-bot commented on Jan 20, 2023

    @melvin-bot

    @roryabraham Whoops! This issue is 2 days overdue. Let's get this updated quick!

  6. roryabraham commented on Jan 20, 2023

    @roryabraham
    ContributorAuthor

    Still actively working on this, implementing it directly in #13118, which is now on HOLD again.

  7. JmillsExpensify commented on Jan 25, 2023

    @JmillsExpensify
    Contributor

    That PR is now merged!

  8. roryabraham commented on Feb 4, 2023

    @roryabraham
    ContributorAuthor

    This is done

  9. MelvinBot commented on Apr 4, 2023

    @MelvinBot
    Contributor

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staffNewFeatureSomething to build that is a new item.ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions