search

webcomponents / custom-elements-manifest

A file format for describing custom elements
BSD 3-Clause "New" or "Revised" License
371 stars 27 forks source link

Custom Element Status #85

Open PaulHMason opened 3 years ago

PaulHMason commented 3 years ago

It would be useful to have a "status" field (free text). I'd use it for something like this:

justinfagnani commented 2 years ago

I don't really think we could regularize this well, personally. Since npm packages are semver versioned, packages can have pre-release suffixes like any other.

I presume a catalog-type app would not show preview releases by default, but could be configured to as an option.

daKmoR commented 2 years ago

an npm package could contain many components... some could be stable, some could be alpha... so a "state" per component could be useful to display to users in a readme or documentation site 🤗

break-stuff commented 1 month ago

I would love this. Right now we are using this plugin to add a custom property to the manifest through a jsDoc tag. It would be great if it were part of the actual schema.