Skip to content

CU - Stop using .sort #10576

Open
Open
@batemapf

Description

@batemapf

Proposed Change

Minimize the use of .sort in the frontend; instead push sorting activities down to the API layer. Includes the .sort referenced in this PR convo on the medical records feature.

Why Should We Prioritize?

Reduces load on client device.

Coding Time Estimation

Large (but with low confidence, depends on how easy/hard API layer changes are. Needs evaluation of each case. where .sort is used.

Testing Considerations

All areas where .sort is/was used.

Checklist

  • Add the relevant team label (Health, global, design system, API, Qa and Release etc.)
  • Attach to ticket to the relevant Team Tech Debt Epic epic (old frontend engineering epic is no longer in use as each team is managing their code's technical debt and code upkeep work)

Metadata

Metadata

Assignees

No one assigned

    Labels

    API teamQATickets require QA work / reviewcode upkeepfront-endTicket requires front-end workglobalIssues for the global team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions