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

Update dependecies. #17436

Merged
merged 3 commits into from Sep 5, 2015
Merged

Update dependecies. #17436

merged 3 commits into from Sep 5, 2015

Conversation

XhmikosR
Copy link
Member

@XhmikosR XhmikosR commented Sep 2, 2015

/CC @cvrebert

@@ -28,7 +28,7 @@
"requireSpaceAfterLineComment": true,
"requireSpaceBeforeBinaryOperators": ["+", "-", "/", "*", "=", "==", "===", "!=", "!==", ">", "<", ">=", "<="],
"requireSpaceBetweenArguments": true,
"requireSpacesInAnonymousFunctionExpression": { "beforeOpeningCurlyBrace": true, "beforeOpeningRoundBrace": true },
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was the rule removed from JSCS itself, or do we not currently comply with it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It just fails but I'm not sure if it's a regression or intentional.
On Sep 2, 2015 10:09, "Chris Rebert" notifications@github.com wrote:

In js/.jscsrc
#17436 (comment):

@@ -28,7 +28,7 @@
"requireSpaceAfterLineComment": true,
"requireSpaceBeforeBinaryOperators": ["+", "-", "/", "*", "=", "==", "===", "!=", "!==", ">", "<", ">=", "<="],
"requireSpaceBetweenArguments": true,

  • "requireSpacesInAnonymousFunctionExpression": { "beforeOpeningCurlyBrace": true, "beforeOpeningRoundBrace": true },

Was the rule removed from JSCS itself, or do we not currently comply with
it?


Reply to this email directly or view it on GitHub
https://github.com/twbs/bootstrap/pull/17436/files#r38503896.

@XhmikosR
Copy link
Member Author

XhmikosR commented Sep 5, 2015

bump

@cvrebert
Copy link
Collaborator

cvrebert commented Sep 5, 2015

Perhaps we could punt JSCS to another PR/issue for further investigation, and merge everything else?

@XhmikosR
Copy link
Member Author

XhmikosR commented Sep 5, 2015

I can split it if you think it's better, sure.

@XhmikosR
Copy link
Member Author

XhmikosR commented Sep 5, 2015

Done.

@cvrebert
Copy link
Collaborator

cvrebert commented Sep 5, 2015

:shipit: as soon as Travis passes.

XhmikosR added a commit that referenced this pull request Sep 5, 2015
@XhmikosR XhmikosR merged commit 380e200 into v4-dev Sep 5, 2015
@XhmikosR XhmikosR deleted the v4-dev-xmr-deps branch September 5, 2015 05:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants