custom-elements-manifest icon indicating copy to clipboard operation
custom-elements-manifest copied to clipboard

A file format for describing custom elements

Results 59 custom-elements-manifest issues
Sort by recently updated
recently updated
newest added

The path property here: https://github.com/webcomponents/custom-elements-manifest/blob/e527701c69ebebff1cfb85299bf54d839def0061/schema.d.ts#L52 is? relative to this file or relative to the package.json? has the extension within?

Documented here: https://github.com/webcomponents/custom-elements-manifest/pull/70 As in some situations, the tooling might not have access to a package.json, it would be beneficial to be able to indicate the location of the custom...

Consider this case ```js class MyElement extends HTMLElement { constructor() { super().attachShadow({ mode: 'open' }).innerHTML = ` :host { color: var(--my-color, red); } @media (prefers-color-scheme: dark) { :host { color:...

APIs need a way to describe object interfaces in a way that documentation can describe. ClassDeclaration has most of what we need, but includes some fields not suitable for interfaces.

What do we need to capture in the description file?

@justinfagnani sometimes attributes&properties are linked to a specific event like it was in polymer. or in lit with this addon: https://github.com/morbidick/lit-element-notify shouldn't this also be reflected in the schema?

I think it would be helpful to specify a version for the custom element. For example, if I add a few major properties/events to an element, I should be able...

It would be helpful to mark a class field or property as readonly (i.e. getter only or defined as writable: false) ![Screenshot_2020-12-17 Components apollo-client Apollo Elements](https://user-images.githubusercontent.com/1466420/102488281-7cda5700-4074-11eb-8a74-52753f2bf822.png) ```json { "name": "elements",...