Skip to content

Conversation

@bart-degreed
Copy link
Contributor

Fixes #791.

Adds support for best-effort paging links (in case the total number of resources is unknown). This strategy is also applied on all secondary resources, as it is quite complex to determine total resource count.

  • Fixed: exception on pass-through query string parameter in secondary request
  • Optimization: skip query execution for primary resource if total count is zero
  • Fixed: self link was calculated twice (in different ways) when paging active
  • Fixed: nested page size was lost when rendering paging links
  • Fixed: invalid paging links on secondary endpoints
  • Fixed: cases where self link was different from the actual URL being requested (we now leave page number/size in, even when they match the default)

Bart Koelman added 2 commits September 25, 2020 10:12
…f resources is unknown). This strategy is also applied on all secondary resources, as it is quite complex to determine total resource count.

Fixed: exception on pass-through query string parameter in secondary request
Optimization: skip query execution for primary resource if total count is zero
Fixed: self link was calculated twice (in different ways) when paging active
Fixed: nested page size was lost when rendering paging links
Fixed: invalid paging links on secondary endpoints
Fixed: cases where self link was different from the actual URL being requested (we now leave page number/size in, even when they match the default)
@bart-degreed bart-degreed requested a review from maurei September 25, 2020 08:46
@maurei maurei merged commit 4ebc9ce into json-api-dotnet:master Sep 28, 2020
@bart-degreed bart-degreed deleted the best-effort-paging branch September 29, 2020 07:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Feature: provide best-effort paging links when total count is unknown

2 participants