Query aggregated object endpoint changes
Closed this issue · 0 comments
Description
This issue is part of #291.
Query aggregated object has two endpoints get fetch aggregated objects. This is done by either providing an id in the URL or with a body containing filters.
These two endpoints should be grouped together under the same endpoint since they are related.
NOTE: Front-end needs changes as well. There is only one front-end issue here eiffel-community/eiffel-intelligence-frontend#252, that you can assign yourself to if you've taken part in a restructure issue.
Motivation
Part of the endpoint restructure.
Exemplification
The will now share the /aggregated-objects endpoint.
Only the two top ones are relevant to this issue.
The /queryMissedNotifications should be removed when doing this implementation since that one will be handled in #346
| Method | Old | New |
|---|---|---|
| GET | /queryAggregatedObject?ID={id} | /aggregated-objects/{id} |
| POST | /query | /aggregated-objects/query |
| GET | /queryMissedNotifications?subscriptionName=Sub1,Sub2,Sub3 | /failed-notifications?name=Sub1,Sub2,Sub3 |
Benefits
This makes all endpoints look and behave the same way.