Docs: clarify the default behavior of operator-linebreak (fixes #7459)
#7726
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
|
@not-an-aardvark, thanks for your PR! By analyzing the history of the files in this pull request, we identified @scriptdaemon, @BenoitZugmeyer and @BYK to be potential reviewers. |
2 tasks
not-an-aardvark
force-pushed
the
operator-linebreak-docs
branch
from
cefa513
to
91f7a97
Compare
|
LGTM |
ilyavolodin
approved these changes
Dec 9, 2016
gyandeeps
approved these changes
Dec 9, 2016
eslint-deprecated
bot
added
the
archived due to age
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What is the purpose of this pull request? (put an "X" next to item)
[x] Documentation update
What changes did you make? (Give an overview)
The default behavior for
operator-linebreakis to use the"after"option with overrides for the?and:operators. However, the documentation incorrectly implied that the overrides were always present when using the"after"option, which is not the case. The overrides are part of the default configuration, but they aren't related to the"after"option.(fixes #7459)
Is there anything you'd like reviewers to focus on?
Nothing in particular.