Consistency pass on href outputs #18
Open
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
Now they all have double quotes and all processed as safe, so it doesn't end up with HTML codes in the output URL
|
I recommend squashing & merging this if you accept it, since I had to make two commits! |
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.
Now they all have double quotes and all processed as safe, so it doesn't end up with HTML codes in the output URL.
For example, before this change, the
<head>section would contain raw code as such:After this change, the raw output is more consistent and clear:
Similarly, the site header links were not processed as
safeso they also looked similarly odd in the raw code.