Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Polymer: missing Dart class to define a custom element isn't diagnosed #14253

Closed
DartBot opened this issue Oct 20, 2013 · 2 comments
Closed

Polymer: missing Dart class to define a custom element isn't diagnosed #14253

DartBot opened this issue Oct 20, 2013 · 2 comments
Labels
closed-duplicate Closed in favor of an existing report

Comments

@DartBot
Copy link

DartBot commented Oct 20, 2013

This issue was originally filed by serg...@chromium.org

When the Dart implementation source included from a custom element Xyz's definition doesn't contain a class tagged by @­CustomTag('xyz'), the element is broken (doesn't instantiate/render), but no useful diagnostic is produced.

One common use case is starting with synchronized <polymer-element> and @­CustomTag names, then renaming one and forgetting to rename the other. The element silently breaks.
@madsager
Copy link
Contributor

Added Area-Polymer, Triaged labels.

@jmesserly
Copy link

Added Duplicate label.
Marked as being merged into #14054.

@DartBot DartBot added Type-Defect closed-duplicate Closed in favor of an existing report labels Oct 21, 2013
@jmesserly jmesserly mentioned this issue Jun 3, 2015
Closed
@DartBot DartBot mentioned this issue Jun 5, 2015
Closed
@kevmoo kevmoo mentioned this issue Jun 5, 2018
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-duplicate Closed in favor of an existing report
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kevmoo @jmesserly @madsager @DartBot