Fix hard breaks for weak keywords. #363
Closed
Conversation
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
The two trailing spaces to indicate a hard break were missing for the list of weak keywords.
|
Note: Using a trailing backslash might be safer than relying on invisible markup, but using spaces follows the style of the rest of the project. |
|
LGTM. If you want to switch to trailing backslash, I'd be okay with that too, given both me and another person have inadvertently tried deleting them already... |
|
@alercah @matthewjasper on question of trailing backslashes |
|
👍 on trailing backslashes |
|
Closing in favor of #365 |
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.
The two trailing spaces to indicate a hard break were missing for
the list of weak keywords.