Skip to content

Paginate template history #53

Closed

Description

@kylecarbs

Acceptance Criteria
Querying project history returns every entry in the database. This should be paginated.

Implementation Details

Activity

  1. stale commented on Feb 6, 2022

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.

  2. added
    staleThis issue is like stale bread.
    on Feb 6, 2022
  3. removed
    staleThis issue is like stale bread.
    on Mar 29, 2022
  4. added this to the V2 Beta milestone on Apr 1, 2022
  5. changed the title [-]Paginate project history[/-] [+]Paginate template history[/+] on Apr 26, 2022
  6. misskniss commented on Apr 26, 2022

    @misskniss

    Use pagination for users as a reference.

  7. misskniss commented on Apr 26, 2022

    @misskniss
  8. Emyrk commented on Apr 26, 2022

    @Emyrk
    Member

    Users are paginated as a reference. Would be great to generalize parts that we can, but up to the implementer if that is at this endpoint, or a future pagination one to reuse code between.

    Sql:

    -- name: GetUsers :many

    Route:

    func (api *api) users(rw http.ResponseWriter, r *http.Request) {

  9. mafredri commented on May 2, 2022

    @mafredri
    Member

    Does this issue refer to the /templates or the /templateversions endpoint under /api/v2/organizations/{organization}? Or is it another one entirely?

  10. kylecarbs commented on May 2, 2022

    @kylecarbs
    MemberAuthor

    I think /templateversions is more important immediately. It's reasonable to expect hundreds of versions of a template, even on a small scale deployment.

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

Metadata

Metadata

Labels

apiArea: HTTP API

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions