This resolves the issue when paginating over 'nested' resources. In stead of injecting a parent object into resource that manages the childs, we just retrieve the childs from a custom resource path (that happens to include the parent id).
For now this is a POC: it only works for subscriptions (nested below a customer) and subscription payments (nested below customer and subscription).
Related to #315
This resolves the issue when paginating over 'nested' resources. In stead of injecting a parent object into resource that manages the childs, we just retrieve the childs from a custom resource path (that happens to include the parent id).
For now this is a POC: it only works for subscriptions (nested below a customer) and subscription payments (nested below customer and subscription).