You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried getting devices by tenant Id with pagination but this api behaving incorrectly.
i.e- If you have 10 devices in a tenant, and you want to show 8 in a page then, the api is giving every pageOffset 8 records that is wrong, and also the filter json is not working, please have look into this issue.
If you believe that there is also an issue with filtering results, then please create a dedicated issue for the specific problem that you experience. A statement like
the filter json is not working
is not helpful without any context and detail information.
I have created some additional unit tests in order to be able to reproduce the erroneous behavior. However, the unit tests all succeed and I have no clue (yet) why this would fail on the Sandbox. Next step will be to add some integration tests as well ...
I have created some additional unit tests in order to be able to reproduce the erroneous behavior. However, the unit tests all succeed and I have no clue (yet) why this would fail on the Sandbox. Next step will be to add some integration tests as well ...
I have extended the unit and integration tests in PR #3541 but they all succeed locally. Do you experience the erroneous behavior also with a local installation of Hono?
I've tried getting devices by tenant Id with pagination but this api behaving incorrectly.
i.e- If you have 10 devices in a tenant, and you want to show 8 in a page then, the api is giving every pageOffset 8 records that is wrong, and also the filter json is not working, please have look into this issue.
1: API URL - https://hono.eclipseprojects.io:28443/v1/devices/My-Tenant?pageSize=8&pageOffset=0 is showing 8 records.
2: API URL - https://hono.eclipseprojects.io:28443/v1/devices/My-Tenant?pageSize=8&pageOffset=1 is also showing 8 records, it should be 2 only.
Also please have look on filterJson issue.
The text was updated successfully, but these errors were encountered: