add support for tracker v41

[eperedo]

📌 References

• Issue: Closes https://app.clickup.com/t/86964a9ua

📝 Implementation

• In v41 the tracker endpoints /tracker/trackedEntities, /tracker/events and /tracker/enrollments no longer returns the data in an instances array anymore. Now they are using a key named after the plural of the returned entity.

/tracker/trackedEntities

{
  "trackedEntities": [...]
}

/tracker/events

{
  "events": [...]
}

/tracker/enrollments

{
  "enrollments": [...]
}

In order to keep backwards compatibility and to avoid breaking changes in d2-api we'll keep the instances attribute checking for an instances array and if there's none we fall back to trackedEntities, events or enrollments according to the requested endpoint.

• Also now the pagination information is included in a pager object:

{
  "pager": {
    "page": 3,    
    "pageSize": 2,
    "total": 373570,
    "pageCount": 186785,
  },
  "page": 3,
  "pageSize": 2,
  "total": 373570,
  "pageCount": 186785,
}

They are also keeping the pagination information outside the object for now, but it will be removed in a future release.

📹 Screenshots/Screen capture

🔥 Notes to the tester

Can you help me with a beta version, please? @adrianq

#86964a9ua

[ifoche]

Task linked: CU-86964a9ua A12: Testing and feedback

[tokland]

Some in-line comments:

[tokland]

type TrackedKey. It seems plural, because of the enumeration, but in fact it's describing a value that will have some of this value, not a collection.

[tokland]

Cool, just some minor changes (already commited) and comments that need no action:

[tokland]

a ? a : b -> a || b

[tokland]

We set this prop as optional, that was the logic what motivated the a || b logic. And also pager?: TrackedPager in the 3 tracker responses from the api.

[tokland]

To be struct, now we don't have always TrackedPager, in the future it will disappear. But since the logic to handle this is not trivial, let's leave as is, the runtime logic is correct.