search

cake-build / website

:earth_americas: The Cake website: https://cakebuild.net
https://cakebuild.net
MIT License
42 stars 230 forks source link

Show supported runners on extension detail page #1403

Open pascalberger opened 3 years ago

pascalberger commented 3 years ago

Follow up of https://github.com/cake-build/website/issues/580 and https://github.com/cake-build/website/issues/299. With the combination of Cake version the addin references and TFM we can decide with which runners it is compatible with based on the supported platform table. An addin should be classified as compatible with a runner as soon as it targets a TFM, which is compatible with a runner. It shouldn't matter if an addin targets netstandard2.0 or e.g. multi-targets net641 and netcoreapp3.0.

This is of course only from a technical point of view, it's still possible that e.g. an addin targeting netstandard2.0 doesn't work on Cake .NET Tool on Linux. We should mention this in a tooltip.

Addin targeting .NET Standard 2.0:

image

Addin multi-targeting:

image

Add referencing latest Cake version but doesn't support all runners:

image

Addin referencing old Cake version and TFM:

image

pascalberger commented 3 years ago

This probably can be done in Addin Discoverer as part of the compliance score calculation (https://github.com/cake-contrib/Cake.AddinDiscoverer/issues/156) and written to YAML file