Tools: Polymer Element public API shouldn't be in custom elements extending Polymer.Element

Created on 28 Aug 2017 · 4Comments · Source: Polymer/tools

When you have an custom element extending Polymer.Element, all public API of polymer is shown.

class KkElement extends Polymer.Element {
...

Otherwise, if your custom element extends a mixin, Polymer API is not listed.

  /**
   * @polymerMixin
   */
  Foo = superClass => class FooMixin extends superClass {
  };

  class KkElement extends Foo(Polymer.Element) {
  ...

analyzer

Source

manolo

👍1

Most helpful comment

a41

limonte on 1 Nov 2017

😄10

All 4 comments

a41

limonte on 1 Nov 2017

😄10

It is possible to use a workaround until proper solution will be implemented.
Workaround: class SomeElement extends (class extends Polymer.Element {})

yuriy-fix on 1 Nov 2017

👍4

I dont see this behavior after removing @extends Polymer.Element from jsdoc... not sure its a valid thing to do though

mgibas on 15 Nov 2017

👍1

This should be solved in iron-component-page, perhaps by hiding inherited properties by default, or otherwise downplaying them.

From a static analysis perspective, if Foo extends Bar, then Foo also inherits Bar's public API. The reason adding a mixin removes those entries from your iron-component-page results is that mixins currently defeat polymer-analyzer's analysis, but that shouldn't be relied upon.