Skip to content
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

Docs: fix possible typo #10060

Merged
merged 1 commit into from Mar 6, 2018
Merged

Docs: fix possible typo #10060

merged 1 commit into from Mar 6, 2018

Conversation

@vsemozhetbyt
Copy link
Contributor

@vsemozhetbyt vsemozhetbyt commented Mar 6, 2018

What is the purpose of this pull request? (put an "X" next to item)

[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

The removed part seems wrong, like copy-paste artifact.

Is there anything you'd like reviewers to focus on?

No. Sorry if I am wrong.

@eslint eslint bot added the triage label Mar 6, 2018
Copy link
Member

@platinumazure platinumazure left a comment

LGTM, thanks for contributing! Just want another set of eyes on this.

@@ -42,7 +42,7 @@ String option:

* `"always"` (default) requires quotes around all object literal property names
* `"as-needed"` disallows quotes around object literal property names that are not strictly required
* `"consistent"` enforces a consistent quote style requires quotes around object literal property names
* `"consistent"` enforces a consistent quote style

This comment has been minimized.

@not-an-aardvark

not-an-aardvark Mar 6, 2018
Member

Could this be expanded to something like:

"consistent" enforces a consistent quote style; in a given object, either all of the properties should be quoted, or none of the properties should be quoted.

My concern is that "a consistent quote style" could be misinterpreted, given that all of the options enforce some level of "consistency" (on the level of an entire codebase rather than an individual object).

This comment has been minimized.

@vsemozhetbyt

vsemozhetbyt Mar 6, 2018
Author Contributor

Done.

@aladdin-add aladdin-add merged commit 66a1e9a into eslint:master Mar 6, 2018
5 checks passed
5 checks passed
commit-message Commit message follows guidelines
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
licence/cla Contributor License Agreement is signed.
Details
release-monitor No patch release is pending
Details
@vsemozhetbyt vsemozhetbyt deleted the vsemozhetbyt:patch-1 branch Mar 6, 2018
This was referenced Mar 22, 2018
@eslint eslint bot locked and limited conversation to collaborators Sep 3, 2018
@eslint eslint bot added the archived due to age label Sep 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.