-
Notifications
You must be signed in to change notification settings - Fork 52
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
Correctly match newlines whitin htmltags. #122
Open
pharixces
wants to merge
2
commits into
caxy:master
Choose a base branch
from
pharixces:bugfix/match_newlines_in_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 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
<options> | ||
<option type="boolean" name="setKeepNewLines" value="true" /> | ||
<option type="boolean" name="setPurifierEnabled" value="false" /> | ||
</options> | ||
|
||
<oldText> | ||
<li | ||
attribute="value"> | ||
value | ||
</li> | ||
</oldText> | ||
|
||
<newText> | ||
<li | ||
attribute="value"> | ||
newvalue | ||
</li> | ||
</newText> | ||
|
||
<expected> | ||
<li | ||
attribute="value"> | ||
<del class="diffmod">value</del><ins class="diffmod">newvalue</ins> | ||
</li> | ||
</expected> |
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.
Alternatively we could add the
s
(PCRE_DOTALL
) modifier so that the dot would match newlines as well.However, this might seem more clear? Are there situations where this change would actually affect the outcome in a negative way?
I think it's technically allowed to have
>
within an attribute value of an HTML tag...that's technically valid I think?
So are we better off adding the
s
modifier to solve this instead?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've tested all regexes (current, mine, yours) with the example you provided and they all break the tag in the
data-some-value
contents. So this is currently a problem and i dont know how to fix this particular issue.However, i do agree the dotall modifier is more clear, i will change the merge request to use that.