spring-projects / spring-projects/spring-data-rest

PagedResources

Open
#89 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: waiting-for-triage
Dominant language
Java
Stars
958
Forks
568
PR merge metrics
No merged PRs in 30d

Description

It appears that RepositorySearchController and RepositoryEntityController both no longer return a PagedResources object and instead use PageResource. Is this due to needing to support Neo4j and MongoDb? It is very handy to be able to get the total elements out of the page object without having to get all objects.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading RepositorySearchController and RepositoryEntityController, then trace how PageResource and PagedResources are produced for repository responses. Compare the pagination metadata exposed for Neo4j and MongoDB, especially total elements; done means establishing the intended response contract and documenting or implementing the required behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
api, backend, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.