fix(eslint-config-enterprise): update eslint-plugin-html #1440
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Markiewic
force-pushed
the
fix/eslint
branch
from
d371295
to
0ad1ca1
Compare
eslint-plugin-html disables the rest of the rules applied to html files. this issue has been fixed in: BenoitZugmeyer/eslint-plugin-html#176 fixup! fix(eslint-config-enterprise): update eslint-plugin-html Revert "fix(eslint-config-enterprise): update eslint-plugin-html" This reverts commit d7b0343. Revert "fixup! fix(eslint-config-enterprise): update eslint-plugin-html" This reverts commit 0ad1ca1.
Markiewic
force-pushed
the
fix/eslint
branch
from
0ad1ca1
to
b3c48bb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
eslint-plugin-htmldisables the rest of the rules applied to html files. This issue has been fixed in: BenoitZugmeyer/eslint-plugin-html#176PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?