Prevent non keywords from accidentally matching on type formatting #2364
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.
Motivation
Closes #2301
Our regexes for matching when to add the
end
token were a little too permissive. We were accidentally matching something likeclass: "bg-white"
as aclass
keyword.Implementation
The reality is that there are only two possibilities for all of the keywords we provide on type formatting for: either there needs to be a space right after the keyword or they need to be at the end of the line.
Automated Tests
Added a test to ensure we don't regress.