Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pagination

Open
#150 0 comments 0 reactions 1 assignee View on GitHub

@sima-qian is already working on this.

Since Oct 19, 2018.

Assessment

This issue has not been assessed yet.

Description

server

Pagination in API responses is always really annoying to handle. It would be good to extract the logic for handling that since you have to use it a few times.

The processPage here seems like a useful starter.

Also, rather than

records.forEach(record => {
  caseTitles.push({
    title: record.get("case_title"),
    id: record.get("primary_key")
  });
});

You could try using map like:

caseTitles.push(records.map(record => ({ title: record.get('case_title'), id: record.get('primary_key')}))

Or similar (I haven't run the example). I think it makes the intent clearer, especially if you extracted the lambda in the map into something with a descriptive name.

Dominant language
JavaScript
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fac-14/OSCEBossKey

All issues in fac-14/OSCEBossKey

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.