Merge `versions` and `assets`?

[jsdelivr]

Merge `versions` and `assets`?

[tomByrer]

No; I cannot think of a use-case to need versions without the assets listing, aside from finding a current version, but we have lastversion already.
Thanks for asking!

[tomByrer]

There is 1 caveat: could be grabbing 100s of lines of JSON just to get a versions listing if it happens to be needed. (Times like this makes me wish I wasn't the only one replying to your ideas :)

[bebraw]

Yeah, it's true assets can come with a big overhead. I guess the question here is, is it worth the simplification? We can keep the API as is. It's easy enough to filter out redundant data in the query if needed so the duplication doesn't hurt that much.

[tomByrer]

Maybe I'm stuck in my old ways when I had to ask the DB sysadmin to make smaller queries to not to overwhelm my Excel spreadsheet on a Pentium II? I could be wrong in envisioning the dataset growing 30x in the next 1-2 years....

Is it better to do as you wish now, & if someone needs a sub-set query latter, then that can be (re-)added? I'm personally indifferent; I'm just looking at worse-case scenarios.

[bebraw]

Let's skip the merge. Even though there is some redundancy it doesn't hurt given you can filter out data you want and this way you won't be getting any extra if you want just versions.