Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ [REST API] Implement sorting functionality in /{scopeId}/endpointInfos API #4090

Merged
merged 1 commit into from
Jul 31, 2024

Conversation

MDeLuise
Copy link
Contributor

Summary

This pull request introduces sorting capabilities to the '/{scopeId}/endpointInfos' API endpoint by adding two new query parameters: sortDir and sortParam.

Details

  • sortDir: Accepts NULL/ASCENDING/DESCENDING, and determines the order of sorting.
  • sortParam: Defines the field by which the sorting is applied.

This enhancement mirrors the sorting functionality already available in other API endpoints, such as /devices. By using these parameters, users can now sort the endpoint information based on any specified field in either ascending or descending order.

Example Usage

To sort the endpoint information in ascending order by a specific field, the request would look like:
GET /{scopeId}/endpointInfos?sortDir=ASCENDING&sortParam=<field_name>
This update enhances the flexibility and usability of the API by providing consistent sorting behavior across different endpoints.

…' endpoint

Implemented sorting functionality for the '/{scopeId}/endpointInfos' API by adding query parameters `sortDir` and `sortParam`. This feature allows sorting of endpoint information based on the specified field (`sortParam`) in either ascending or descending order
@MDeLuise MDeLuise changed the title ✨ [REST API] Implement sorting functionality in '/{scopeId}/endpointInfos' API ✨ [REST API] Implement sorting functionality in /{scopeId}/endpointInfos API Jul 31, 2024
Copy link

codecov bot commented Jul 31, 2024

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 16.75%. Comparing base (62722f7) to head (bdbed8e).
Report is 4 commits behind head on develop.

Files Patch % Lines
.../app/api/resources/v1/resources/EndpointInfos.java 0.00% 4 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff              @@
##             develop    #4090      +/-   ##
=============================================
- Coverage      16.79%   16.75%   -0.04%     
  Complexity        22       22              
=============================================
  Files           2016     2016              
  Lines          52317    52357      +40     
  Branches        4407     4417      +10     
=============================================
- Hits            8787     8773      -14     
- Misses         43132    43184      +52     
- Partials         398      400       +2     
Files Coverage Δ
.../app/api/resources/v1/resources/EndpointInfos.java 0.00% <0.00%> (ø)

... and 5 files with indirect coverage changes

@Coduz Coduz added the Enhancement This PR/Issue improves an part of Kapua label Jul 31, 2024
@Coduz Coduz merged commit ca5615b into eclipse:develop Jul 31, 2024
32 of 34 checks passed
@MDeLuise MDeLuise deleted the improve-sortEndpointInfo branch July 31, 2024 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement This PR/Issue improves an part of Kapua
Projects
Development

Successfully merging this pull request may close these issues.

2 participants