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

get closure-type-checking running again #360

Merged
merged 2 commits into from
May 27, 2016
Merged

get closure-type-checking running again #360

merged 2 commits into from
May 27, 2016

Conversation

samthor
Copy link
Contributor

@samthor samthor commented May 26, 2016

@brendankenny

This gets us up and running again, at least with warnings, not errors.

This works around #954 in an interesting way, but I have some thoughts on fixing that properly too.

@samthor samthor force-pushed the closure-fix branch 2 times, most recently from 5842496 to 30f3793 Compare May 26, 2016 09:02
@@ -1,6 +1,6 @@
language: node_js
node_js:
- "5.0"
- "5.1"
Copy link
Member

Choose a reason for hiding this comment

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

why does this matter?

Copy link
Member

Choose a reason for hiding this comment

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

ah, if this was for the build failure, this won't help :) Rest parameters were added in 6

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed this in the method.

@brendankenny
Copy link
Member

reviewed! Current build failure should be fixed by not using rest parameters while we still support node 5.

@samthor
Copy link
Contributor Author

samthor commented May 27, 2016

@brendankenny this should be good to go now. I've got more fixes in a follow-up patch.

@brendankenny
Copy link
Member

nice job! LGTM

@@ -206,7 +206,7 @@ class Aggregate {
// TODO(paullewis): Remove once coming soon audits have landed.
if (expected[e].comingSoon) {
subItems.push({
value: String.raw`¯\_(ツ)_/¯`,
value: '¯\\_(ツ)_/¯', // TODO(samthor): Patch going to Closure, String.raw is badly typed
Copy link
Contributor

Choose a reason for hiding this comment

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

Noooooooooo!

Fine.

@paullewis paullewis added the +2 label May 27, 2016
@brendankenny brendankenny merged commit 9ff0e36 into master May 27, 2016
@brendankenny brendankenny deleted the closure-fix branch May 27, 2016 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants