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?
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.