-
Notifications
You must be signed in to change notification settings - Fork 30k
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
tools: enable block-spacing in .eslintrc #10377
Closed
Closed
+24
−23
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
In preparation for enabling an ESLint rule, use consistent block spacing. This changes only six files in the code base as block spacing is consistent throughout the rest of the code base. Before: function(c) {data += c;} After: function(c) { data += c; }
Enable rule to enforce consistent use of space between the `{` and `}` that surround a code block and the code block itself. This enforces via linting the de facto standard in the code base.
Trott
added
test
Issues and PRs related to the tests.
tools
Issues and PRs related to the tools directory.
labels
Dec 21, 2016
1 task
addaleax
approved these changes
Dec 21, 2016
lpinca
approved these changes
Dec 21, 2016
gibfahn
approved these changes
Dec 21, 2016
targos
approved these changes
Dec 21, 2016
julianduque
approved these changes
Dec 21, 2016
cjihrig
approved these changes
Dec 21, 2016
julianduque
pushed a commit
that referenced
this pull request
Dec 21, 2016
In preparation for enabling an ESLint rule, use consistent block spacing. This changes only six files in the code base as block spacing is consistent throughout the rest of the code base. Before: function(c) {data += c;} After: function(c) { data += c; } PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
julianduque
pushed a commit
that referenced
this pull request
Dec 21, 2016
Enable rule to enforce consistent use of space between the `{` and `}` that surround a code block and the code block itself. This enforces via linting the de facto standard in the code base. PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
evanlucas
pushed a commit
that referenced
this pull request
Jan 3, 2017
In preparation for enabling an ESLint rule, use consistent block spacing. This changes only six files in the code base as block spacing is consistent throughout the rest of the code base. Before: function(c) {data += c;} After: function(c) { data += c; } PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
evanlucas
pushed a commit
that referenced
this pull request
Jan 3, 2017
Enable rule to enforce consistent use of space between the `{` and `}` that surround a code block and the code block itself. This enforces via linting the de facto standard in the code base. PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
evanlucas
pushed a commit
that referenced
this pull request
Jan 4, 2017
In preparation for enabling an ESLint rule, use consistent block spacing. This changes only six files in the code base as block spacing is consistent throughout the rest of the code base. Before: function(c) {data += c;} After: function(c) { data += c; } PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
evanlucas
pushed a commit
that referenced
this pull request
Jan 4, 2017
Enable rule to enforce consistent use of space between the `{` and `}` that surround a code block and the code block itself. This enforces via linting the de facto standard in the code base. PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
MylesBorins
pushed a commit
that referenced
this pull request
Jan 23, 2017
Enable rule to enforce consistent use of space between the `{` and `}` that surround a code block and the code block itself. This enforces via linting the de facto standard in the code base. PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
MylesBorins
pushed a commit
that referenced
this pull request
Jan 23, 2017
In preparation for enabling an ESLint rule, use consistent block spacing. This changes only six files in the code base as block spacing is consistent throughout the rest of the code base. Before: function(c) {data += c;} After: function(c) { data += c; } PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
MylesBorins
pushed a commit
that referenced
this pull request
Jan 24, 2017
Enable rule to enforce consistent use of space between the `{` and `}` that surround a code block and the code block itself. This enforces via linting the de facto standard in the code base. PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
MylesBorins
pushed a commit
that referenced
this pull request
Jan 24, 2017
In preparation for enabling an ESLint rule, use consistent block spacing. This changes only six files in the code base as block spacing is consistent throughout the rest of the code base. Before: function(c) {data += c;} After: function(c) { data += c; } PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
Merged
MylesBorins
pushed a commit
that referenced
this pull request
Jan 31, 2017
Enable rule to enforce consistent use of space between the `{` and `}` that surround a code block and the code block itself. This enforces via linting the de facto standard in the code base. PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
MylesBorins
pushed a commit
that referenced
this pull request
Jan 31, 2017
In preparation for enabling an ESLint rule, use consistent block spacing. This changes only six files in the code base as block spacing is consistent throughout the rest of the code base. Before: function(c) {data += c;} After: function(c) { data += c; } PR-URL: #10377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Julian Duque <julianduquej@gmail.com>
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.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
tools test
Description of change
Enable rule to enforce consistent use of space between the
{
and}
that surround a code block and the code block itself. This enforces via
linting the de facto standard in the code base.
This changes only six files in the code base as block spacing
is consistent throughout the rest of the code base.
Before:
After: