-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elements Shouldn't show Polymer's internal API #147
Comments
Note that just when the simple element extends an empty mixin, the problem is fixed.
Probably the issue might be fixed in the analyzer. |
Something I would really like to see which would fix this nicely is to add checkbox's to enable/disable each source of inherited properties/methods so you can focus on just what you care about. |
Friendly ping to @aomarks. 🙂 |
@manolo Another one liner workaround is: Reference: Polymer/tools#1566 (comment) |
Description
Elements directly extending the Polymer.Element, shouldn't show methods listed in
Polymer.ElementMixin
orPolymer.PropertyEffects
Expected outcome
Create a new element with
polymer init
and addiron-component-page
to its index.html.Since the element does not have any method, the API should look:
Actual outcome
The API of Polymer.Element is listed instead
The text was updated successfully, but these errors were encountered: