Add support for specific platforms

[benoitf]

Hello, based on microsoft/vscode#23251 (comment)

it seems OpenVSX will have to handle platform specific extensions

like

$ ovsx ... --target linux-x64

and then expose extensions for different arches.

[GitMensch]

Some more information:

The vsce feature was included in vsce 1.99.+ and

starting with version 1.61.0, VS Code looks for the extension package that matches the current platform.

More details found at https://code.visualstudio.com/api/working-with-extensions/publishing-extension#platformspecific-extensions and of course - for the client side - https://github.com/microsoft/vscode-vsce.

[amvanbaren]

I'm currently looking at where to fit the target property in the data model.

• It can be put at the Extension level, this allows for diverging versions per target and target specific ratings, reviews and download counts.
• A new entity called ExtensionTarget can be introduced and placed between Extension and ExtensionVersion. This would allow for diverging versions per target, but can keep ratings, reviews and download counts aggregated for all targets.
• It can be added to FileResource, this assumes that whenever a new version is published it is published for all targets. It is also not possible to write a target specific description or specify target specific theming.

the vsce cmd tool defines the target property on ExtensionVersion.
https://github.com/microsoft/vscode-vsce/blob/507fd82e7818104b434d3096b42718b6b1ea1159/src/publish.ts#L153-L155
In the OpenVSX data model the Extension entity has latest and preview properties that refer to ExtensionVersion. Making ExtensionVersion target specific would also make these properties target specific. I don't see how that would work.

This is a big change to the data model that impacts the whole server. Feedback is much appreciated.

[lnicola]

In the OpenVSX data model the Extension entity has latest and preview properties that refer to ExtensionVersion.

CC #386 (comment), assuming it's the same preview.

[GitMensch]

Here's the comment @lnicola referenced, written by @spoenemann:

Ok, then we've been using this flag in a wrong way in Open VSX. Whoever works on this issue should correct the usage of preview as well. [to mean the extension is in preview, not the extension version]

When this fundamental change is done I think the extension+target+extensionversion or extension+extensionversion+target is the reasonable approach.