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
Polymer linter assumes every non-standard HTML tag intends to be a polymer element. #15719
Comments
good point. It might be nice to have some degree of linting about this though. For example, maybe we could tell the linter which tags to ignore, for example using a regex pattern like ng-*. Removed Priority-Unassigned label. |
This comment was originally written by @bgourlie This would still be an issue for user created angular directives that don't have the ng-* prefix, but ignoring the ng-* prefix would be a good start. |
Added this to the Later milestone. |
Removed Library-PolymerLinter label. |
Added Pkg-Polymer label. |
Removed Pkg-Polymer label. |
Removed Library-PolymerBuild label. |
Removed Area-Polymer label. |
Removed this from the 1.6 milestone. |
Removed Polymer-P-1 label. |
Added PolymerMilestone-Next label. |
Removed Polymer-Milestone-Next label. |
This issue has been moved to dart-archive/polymer-dart#372. |
This issue was originally filed by @bgourlie
I am in the process of integrating a polymer web component with an angular app. Within the client.html file that is designated as the entrypoint in the build.dart file, I have an <ng-view> tag. The linter is complaining about it: "definition for Polymer element with tag name "ng-view" not found."
The text was updated successfully, but these errors were encountered: