-
Notifications
You must be signed in to change notification settings - Fork 35
Throw syntax errors for invalid EndTags #73
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
Open
camerondubas
wants to merge
10
commits into
tildeio:master
Choose a base branch
from
camerondubas:fix/end-tags
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
7f24f68
Throw syntax errors for invalid EndTags
camerondubas 0d213ee
Allow trailing whitespace in EngTags
camerondubas 4a756e9
Merge master
camerondubas ca74152
Only allow tag name in closing tags
camerondubas 7b27974
Revert "Only allow tag name in closing tags"
camerondubas c212800
Revert "Merge master"
camerondubas aecb392
Re-apply "Only allow tag name in closing tags"
camerondubas 2b44185
Revert "Re-apply "Only allow tag name in closing tags""
camerondubas 2d27f35
Fix whitespace, and Re-apply "Only allow tag name in closing tags"
camerondubas f3c022c
Fix typo for "contain"
camerondubas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don’t fully understand this conditional (reviewing on mobile so forgive me if I’ve missed something obvious).
Why do we check if
.current().syntaxError
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right that this is confusing, and I feel like there may be a better way to do this.
This check is required since we no longer enter the
beforeAttributeName
orselfClosingStartTag
states, which would reset thetagNameBuffer
. Without this check I was getting invalid tag names that include the whitespace and/or attributes. i.e{tagname: 'div foo="bar"'}
.The
!isSpace(char)
is there to not include whitespace in the tagname, since I had made the decision to allow trailing whitespace in the closing tag. More on that decision in my reply to your other comment.