Feature - returning response headers in SearchResult #29
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.
Summary:
This PR introduces support for returning HTTP headers in SearchResult, allowing the devs which use midpoint-client-java to read headers from response.
Use Case example:
When querying a paginated list of users (e.g., with offset=0 and maxSize=20), it's often useful to know the total count of available records. While there are several ways to return this (e.g., in headers, an envelope, or a separate endpoint), adding it to the headers is the least disruptive to the existing API.
Example Usage:
This change enables fetching totalCount and other response metadata directly from headers without modifying the response body structure. (Note: Midpoint doesn’t currently return totalCount, but a subsequent PR will address this.)
Let me know if any adjustments or refactoring are needed.
Thank you,
Best regards