ЖК Test (пожалуйста, не удаляйте)

в Караганде

In content panel we have many listings. And those listings are always tied to some database model. But not all columns in those listings are columns of their database models. It can often be the columns of related models. And by following all the rules of our API, we should take these relations from different endpoints. But listings are not just arrays of data that can be simultaneously retrieved and then merged together. No. In listings we have pagination, and ordering, and filtering. And how do we paginate, order, and filter related columns if we take them from different endpoints?

That's how:

• Specify relations (e.g. we have to retrieve 20 buildings, for each of them we want all houses, and for each house we want all floors)
• Group API calls by execution order (ones with no dependencies — first, those that depend on them — second, and so forth)
• retrieve the first group by the original filters, ordering and pagination; then, based on the result, retrieve the second group, filtered by the ids (or other fields) of the first group, repeat for the third group, you got the point.
• combine all retrieved data into one list

This way the number of requests we make equals the number of instance types we retrieve, which, as it seems to me, does make sense.