fix(regression): form interpreted as pugScriptLoopRegion #119
+1
−1
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
On the commit 8623141, there was added the `each` keyword to the vim-pug syntax/plug.vim However, it doesn't check if there is a `m` after `for`, making `form` a `pugScriptLoopRegion` instead of a `htmlTagName`
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.
On the commit 8623141, it was added
the
eachkeyword to the vim-pug syntax/plug.vimHowever, it doesn't check if there is a
mafterfor, makingformapugScriptLoopRegioninstead of ahtmlTagName.A single space fixes the issue.
Before:
After:
