What is the story for dev tools to extract metadata of web components?

[dglazkov]

I think @ebidel, @addyosmany, @robdodson have a beautiful story here :smiley:

[ebidel]

I'd love to hear @banguero is looking for? We're working with the DevTools team to expose more stuff and making the tools better from components.

cc @addyosmani

[addyosmani]

We're currently looking at summarizing child elements, attributes, properties and methods of an element when you inspect one. We're also considering highlighting elements involved in a data-binding operation. Anything else you're interested in would be super useful to know at this stage as we've just started planning out a better debugging story :)

[banguero]

Thanks guys. I am particularly wondering if there is (or should there be) anything in the web components spec that indicates how dev tools would discover/query metadata of web components (even if they are not polymer-elements). Is there an API as part of the custom element registration that would allow tools to efficiently implement things like intellisense for attributes when declaring the element in html?

[dglazkov]

These are all awesome questions. The way I would go about answering them is this: custom elements are just DOM elements... and also just JS objects. What API (if any) would the Web platform need to make any DOM element or any JS object discoverable/queriable by a dev tool?