-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Consider using an HTML Linter #3490
Comments
I like the idea! Maybe with |
@abdonrd Does POlylint support pluggable rules? Also HTMLHint is more popular and general purpose linter for HTML and not just Polymer. Any specific feature of polylint thats missing in HTMLHint in your opinion? |
I'm not sure, but @garlicnation maybe can help with it. :) |
@azakus thanks for looking into this. Would like to hear your thoughts! |
@garlicnation Your thoughts? @abdonrd Any Updates? |
@gaurav21r I haven't news. :( |
The new linter supports various linting rules and can be easily extended. The linter is also integrated in the several editor plugins for smooth integration into your workflow. You can still adopt the HTMLHint if you want to into your own build configuration. |
I've observed one of the incidental goals of Polymer (and indeed WebComponents in general) is to try to migrate a lot of imperative JS Code to declarative HTML.
iron-ajax
being a golden example of this.As developers use more and more HTML in their projects (more tags, more nesting, more attributes) I think it should be important to add (and extend) an HTML Linter.
According to our research at rcorp/standard-project-structure#4,
HTMLhint is the best one out there. How about a standard
.htmlhintrc
file for all PolymerElements, Demos and Docs ?If it can be included in the starter kit even better!
The text was updated successfully, but these errors were encountered: