-
-
Notifications
You must be signed in to change notification settings - Fork 380
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
Whitespace inside attribute #310
Labels
bot:stale
Issue marked as stale because there was no activity
feature request
Functionality that introduces a new feature
PR needed
Comments
thedaviddias
added
PR needed
#status: accepted 👍
feature request
Functionality that introduces a new feature
labels
Jan 10, 2019
1 task
thedaviddias
pushed a commit
that referenced
this issue
Feb 23, 2019
* 0.10.3 * feat(htmlhint): add new rule for whitespace in attributes (#310) * fix(htmlhint): removed unnecessary code (#310) * 0.11.0 * Revert "Merge branch 'develop' into attr-whitespace" This reverts commit 35988c1, reversing changes made to 981cca7. * Revert "Revert "Merge branch 'develop' into attr-whitespace"" This reverts commit cfa794d. * chore(htmlhint): rebuilt package.json * chore(htmlhint): updated rule to use ES6 * 0.10.3 * 0.11.0 * fix(htmlhint): made change to test cases and index.js
thedaviddias
pushed a commit
that referenced
this issue
Feb 1, 2020
* 0.10.3 * feat(htmlhint): add new rule for whitespace in attributes (#310) * fix(htmlhint): removed unnecessary code (#310) * 0.11.0 * Revert "Merge branch 'develop' into attr-whitespace" This reverts commit 35988c1, reversing changes made to 981cca7. * Revert "Revert "Merge branch 'develop' into attr-whitespace"" This reverts commit cfa794d. * chore(htmlhint): rebuilt package.json * chore(htmlhint): updated rule to use ES6 * 0.10.3 * 0.11.0 * fix(htmlhint): made change to test cases and index.js
@AbdealiJK I think this was implemented in #322. |
thedaviddias
added a commit
that referenced
this issue
May 13, 2020
* fix: missing test cases (#327) **Fixes**: #325 - [x] Check the commit's or even all commits' message styles matches our requested structure. - [x] Check your code additions will fail neither code linting checks nor unit test. #### Short description of what this resolves: In the original pull request some of the test cases were missing. Added --recursive option for mocha to check for all individual rules. * feat(htmlhint): add new rule for whitespace in attributes (#310) (#322) * 0.10.3 * feat(htmlhint): add new rule for whitespace in attributes (#310) * fix(htmlhint): removed unnecessary code (#310) * 0.11.0 * Revert "Merge branch 'develop' into attr-whitespace" This reverts commit 35988c1, reversing changes made to 981cca7. * Revert "Revert "Merge branch 'develop' into attr-whitespace"" This reverts commit cfa794d. * chore(htmlhint): rebuilt package.json * chore(htmlhint): updated rule to use ES6 * 0.10.3 * 0.11.0 * fix(htmlhint): made change to test cases and index.js * html.js (#304) This is a new formatter which logs error messages in html format on console as well as it will generate a report file in html format **Fixes**: # 🚨 Please review the [guidelines for contributing](CONTRIBUTING.md) and our [code of conduct](../CODE_OF_CONDUCT.md) to this repository. 🚨 **Please complete these steps and check these boxes (by putting an x inside the brackets) before filing your PR:** - [x] Check the commit's or even all commits' message styles matches our requested structure. - [x] Check your code additions will fail neither code linting checks nor unit test. #### Short description of what this resolves: New formatter #### Proposed changes: New formatter ## - - 👍 Thank you! * fix(htmlhint): added rule for special characters in tag name (#146) (#331) **Fixes**: # 🚨 Please review the [guidelines for contributing](CONTRIBUTING.md) and our [code of conduct](../CODE_OF_CONDUCT.md) to this repository. 🚨 **Please complete these steps and check these boxes (by putting an x inside the brackets) before filing your PR:** - [x] Check the commit's or even all commits' message styles matches our requested structure. - [x] Check your code additions will fail neither code linting checks nor unit test. #### Short description of what this resolves: Added rule to check for special characters in tag name. See (#146) #### Proposed changes: ## - - 👍 Thank you! * fix(htmlhint): added rule for quotes around attribute values (#147) (#333) * fix(htmlhint): add ability to pass regexp in config (#328) Based on #238 Add ability to pass regexp in `.htmlhintrc` file for matching attributes value. Example: ```js ... "id-class-value": { "regId": "^[a-z\\d]+([-_]+[a-z\\d]+)*$", "message": "The id and class attribute values must be in lowercase and split by dash or underscore" }, ... ``` Problem was in parsing config file by `JSON.parse`. We can not correct pass `regexp` into json schema. Only `string`. And this `string` after parsing is `string` too. I just check input data. If it is not regexp then create `new RegExp` instance from input string. **Fixes**: # 🚨 Please review the [guidelines for contributing](CONTRIBUTING.md) and our [code of conduct](../CODE_OF_CONDUCT.md) to this repository. 🚨 **Please complete these steps and check these boxes (by putting an x inside the brackets) before filing your PR:** - [ ] Check the commit's or even all commits' message styles matches our requested structure. - [ ] Check your code additions will fail neither code linting checks nor unit test. #### Short description of what this resolves: #### Proposed changes: ## - - 👍 Thank you! * feat(htmlhint): added attribute sorting (#309) (#332) **Fixes**: # 🚨 Please review the [guidelines for contributing](CONTRIBUTING.md) and our [code of conduct](../CODE_OF_CONDUCT.md) to this repository. 🚨 **Please complete these steps and check these boxes (by putting an x inside the brackets) before filing your PR:** - [ ] Check the commit's or even all commits' message styles matches our requested structure. - [ ] Check your code additions will fail neither code linting checks nor unit test. #### Short description of what this resolves: Added sort feature for tag attributes. #### Proposed changes: - ## - - 👍 Thank you! * Used Object.keys instead of Object.values (#344) Used Object.keys instead of Object.values because it is not supported by nodejs before v8. * Create FUNDING.yml (#350) * updates URLs in repository and bugs in package.json (#354) * chore: update commitizen and semantic release (#357) * feat(htmlhint): add RegExp and regex string (#346) RegExp and regex string can be used in whitelist now! related to #228 #183 microsoft/vscode-htmlhint#34 * update links back to htmlhint.com (#359) Co-authored-by: Zhixing Zhang <account@neoto.xin> Co-authored-by: Daman Mulye <dmulye2@illinois.edu> Co-authored-by: nmanupuri <39561219+nmanupuri@users.noreply.github.com> Co-authored-by: orangewit3 <43012690+orangewit3@users.noreply.github.com> Co-authored-by: meetDeveloper <32453612+meetDeveloper@users.noreply.github.com> Co-authored-by: Christian Oliff <christianoliff@yahoo.com> Co-authored-by: New Future <NewFuture@users.noreply.github.com>
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bot:stale
Issue marked as stale because there was no activity
feature request
Functionality that introduces a new feature
PR needed
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Many times, people add unnecessary whitespaces inside some attributes. For example
class=" col-md-2"
and sometimes double space between values in theclass
attributeclass="col-md-2 col-offset-2
Would be nice to give a warning in such cases
Describe the solution you'd like
Would be good to have a rule for "No leading/training spaces in attribute" and maybe another one specifically for
class
attribute to handle that all values should be separated by a single spaceDescribe alternatives you've considered
NA
The text was updated successfully, but these errors were encountered: