Justin Fagnani

Results 256 issues of Justin Fagnani

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?

Demo is an interesting bit of the schema. Right now it's only referenced from `CustomElement#demos`, but really, anything could have an associated demo, including or especially the package as a...

Catalogs and GUI builders would benefit from being able to show a custom icon. This could go in metadata. We should probably look for inspiration from PWA app manifests.

Many analysis tools will use JSDoc tags to determine what web component specific features. To keep from fragmenting the ecosystem around different sets of JSDoc, we should make a recommended...

Beyond goals and motivations as the readme currently has, we need to explain the schema and rationale for some of the decisions.

We want to avoid duplication of data in the schema, but we also want to allow for easily querying a schema, or related collection of schemas. Tools will want to...

This spec has progress and is shipping in Chrome. We should move it into the webcomponents/polyfills repo and figure out a bundle/loader strategy.