Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • G git-eca-rest-api
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse FoundationEclipse Foundation
  • IT
  • APIs
  • git-eca-rest-api
  • Issues
  • #7
Closed
Open
Issue created Apr 03, 2020 by Martin Lowe@malowe🇨🇦Maintainer

Tech debt: Use Link headers to paginate rather than manual pagination

Current Project API pagination is brittle due to the current manual method of pagination within the ProjectsService. This was done as an acceptable stopgap to go live, and a better fix that makes use of Link Headers should be used.

On the initial investigation, there was no found way to easily extend the RESTeasy API builder model. If this model can be extended, then adding a post-process to the responses to attach Link headers to the response output can be used to more sustainably iterate over the data. If there is no way to extend this model, then a concrete implementation will need to be created for the Projects REST API over the generated implementation.

Edited Jan 17, 2022 by Chris Guindon84
Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent