API request filter
Posted: Tue Apr 08, 2025 10:19
Hi
I'm not sure if this should go to feature requests or problems, as I'm sort of hoping it's just something I missed.
Edit: Might as well belong to Developers, not sure. Can admins adjust, if needed, please?
I'm wondering if there is any filtering or-alike available on rest-api requests, so to be able to get("/composition") and not get the entire subtree of all children duplicated and expanded, since we currently get all layers under "layers" tree, but then also same layers in "groups" tree as well, and these all have all clips, with all properties etc.
I feel like getting the composition with just upper "group" and "layer" objects would be great, at least optionally, as we have separate endpoints for getting groups and layers by their ids.
This was nicely solved with thumbnails, for obvious reasons, and its great. Would something like GET "/composition/layergroups/" and its pairs make sense, to be able to get just the "layergroups" subtree, and similar?
It would improve user experience for composition and groups since processing single composition request takes drastically longer compared to just do layer by layer by id until reaching 404 response, it also prevents partitioned feedback response using already available nodes, but mostly lacks support to selectively build composition tree and custom UI.
I'd love to hear some feedback in this regard. Thanks
Partially related, want to report a likely typo -> on https://resolume.com/docs/restapi/#/ the layergroup section has first 7 endpoints for /composition/columns listed.
I'm not sure if this should go to feature requests or problems, as I'm sort of hoping it's just something I missed.
Edit: Might as well belong to Developers, not sure. Can admins adjust, if needed, please?
I'm wondering if there is any filtering or-alike available on rest-api requests, so to be able to get("/composition") and not get the entire subtree of all children duplicated and expanded, since we currently get all layers under "layers" tree, but then also same layers in "groups" tree as well, and these all have all clips, with all properties etc.
I feel like getting the composition with just upper "group" and "layer" objects would be great, at least optionally, as we have separate endpoints for getting groups and layers by their ids.
This was nicely solved with thumbnails, for obvious reasons, and its great. Would something like GET "/composition/layergroups/" and its pairs make sense, to be able to get just the "layergroups" subtree, and similar?
It would improve user experience for composition and groups since processing single composition request takes drastically longer compared to just do layer by layer by id until reaching 404 response, it also prevents partitioned feedback response using already available nodes, but mostly lacks support to selectively build composition tree and custom UI.
I'd love to hear some feedback in this regard. Thanks
Partially related, want to report a likely typo -> on https://resolume.com/docs/restapi/#/ the layergroup section has first 7 endpoints for /composition/columns listed.