That’s understandable. At scale (as an engineer) I can see that it would be cumbersome. Perhaps a separate service designed specifically for resolving this issue? Story Resolver or something similar would make sense. Basically supply the base query and the service iterates through all the components and resolves relations.
That’s basically what I’ve written in my client but it’s slow and cumbersome given the amount of data we’re working with. Something that fetches the data and mitigates the 100-200ms round-trips to the UUID endpoint would save a bit of effort.
Given that SB has received many similar requests and given that this may mitigate effective and/or efficient utilisation of your service, I’d strongly recommend considering it. =)