feat: add missing angular-whitespace converter #1201
Merged
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
JoshuaKGoldberg
added
the
status: waiting for reviewer
|
Probably will drop the 2nd. commit as per #1203 😆 |
|
Apologies for the delay on these: expect a review by the end of the weekend! |
Yeah, that's a tricky one. I think it's fine to leave as-is. The current message of "we don't have an equivalent for this rule" is accurate. |
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.
PR Checklist
status: accepting prsOverview
1st. commit: simplify converters to simply return an empty object, so it's consistent with existing ones (sorry, I didn't realize this before);
2nd. commit: move
import-destructuring-spacingandprefer-inline-decoratorfrom root folder tocodelyzer/;3rd. commit: create a converter for
angular-whitespace.It's still missing the rule
no-unused-css... I don't know if it should be added as it could be potentially be added someday (angular-eslint/angular-eslint#451)... in any case, tell me what to do.