You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Not a problem, hmlhint works very well. I have been using it for xml as well. However, it needs a little tweaking to work ideally with xml.
Describe the solution you'd like
Make modifications to work with xml better (or fork another tool). This could be as simple as adding another option to some of the rules. For example, this is a perfectly valid tag in xml <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>, but it is not valid for html. A way to specify that it is linting xml instead of html could run a variation of the rules where they differ for xml. Perhaps it could be done for other file types as well.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I have looked diligently for an nmp node command line xml linter and tried out many. This is the closest I have found.
Additional context
Another opportunity to expand the uses of this tool would be to make changes for html used with Angular. Some things that are marked as issues when some rules are turned on are actually required by Angular. In like manner, some things that should be avoided in HTML when using Angular in a reactive, instead of a template driven manner, are not caught. It would be nice if these could be caught. Like XML, it would not take a lot of effort to specify that it is being used for Angular html and to modify existing rules accordingly. A few rules could be added to cover anything that is missing.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is your feature request related to a problem? Please describe.
Not a problem, hmlhint works very well. I have been using it for xml as well. However, it needs a little tweaking to work ideally with xml.
Describe the solution you'd like
Make modifications to work with xml better (or fork another tool). This could be as simple as adding another option to some of the rules. For example, this is a perfectly valid tag in xml <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>, but it is not valid for html. A way to specify that it is linting xml instead of html could run a variation of the rules where they differ for xml. Perhaps it could be done for other file types as well.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I have looked diligently for an nmp node command line xml linter and tried out many. This is the closest I have found.
Additional context
Another opportunity to expand the uses of this tool would be to make changes for html used with Angular. Some things that are marked as issues when some rules are turned on are actually required by Angular. In like manner, some things that should be avoided in HTML when using Angular in a reactive, instead of a template driven manner, are not caught. It would be nice if these could be caught. Like XML, it would not take a lot of effort to specify that it is being used for Angular html and to modify existing rules accordingly. A few rules could be added to cover anything that is missing.
The text was updated successfully, but these errors were encountered: