chore: return pagination fields in page objects in /programNotificationInstances TECH-1683 #16245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
skipPaging
query parameter in favor ofpaging
used in most endpoints.pager
used in most endpoints.programNotificationInstances
instead ofinstances
key to align with most other endpointspage
default to 1. Thejavax.persistence
API we use in the store is zero based but this should not be leaked to the user.We will align the controller and its request parameters with tracker exporters at a later stage. Right now we have to duplicate some of the validation logic we have in the RequestParamsValidator.