ccorn

No need to hurry this one. This auto-para branch still needs work. The current state solves most inline+block issues with `dd` elements, but as explained above, there are still cases...

I can confirm that this works in Gitpod as described. Response sizes: ``` 32487536 verquery.json 665435 verquery.v2.json ``` That is a reduction to about 2% of the original response size....

> * **preview**: whether the extension is in preview mode. But that one *is* version-specific. E.g. | Query URL | preview | |:--|:--:| | | false | | | true...

> > For example, this model implies that an extension cannot be renamed or moved to another namespace in a new version. (Can it?) > > Currently it can't. However,...

> I've added the `/api/v3/-/query` endpoint. The response size is ~800 KB, so the `allVersions` entry contributes the most to the response size. Thanks! I will try it. Awesome progress!

> Maybe it is better to err on the side of caution then. In fact, the code mentions `namespaceUuid` and `extensionUuid`, so I suppose that the actual immutable identifiers are...

I have tried this PR at https://github.com/eclipse/openvsx/pull/454/commits/5189e62e9c2d7135fad81bf4ae960f83e836c392 now. As before, I downloaded the responses and, out of curiosity, piped them through `gzip -c | wc -c` and `zstd -c |...

I have tried this PR at ab6a02aa05977daa5405c60a18c9afbaf8714cad in Gitpod. Indeed, v4 is precisely the original response without all the `.allVersions` erntries, as I have wished for. Response sizes with `ìncludeAllversions`:...

What about making the query parameter `includeAllVersions` ternary? | `includeAllVersions` | Meaning | |:-----------------------|:--------------------------------------------| | `false` | no `allVersions`, metadata for one version | | `true` | no `allVersions`, metadata...

> Version links are minimal extension objects. Only `namespace`, `name`, `version` and `url` are specified. Interesting approach. Going to take a look. However, we would need the `engines` sub-objects for...