-
Notifications
You must be signed in to change notification settings - Fork 408
fix(jasmine): support "pending" it
clauses with no test body
#659
Conversation
lib/jasmine/jasmine.ts
Outdated
return testProxyZone.run(testBody, this, [done]); | ||
} : function() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we always return a function, won't it essentially make all specs non-pending (since there will be a callback specified)?
I think this should be:
return testBody && ((testBody.length == 0) ? function() { ... } : function { ... });
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good spot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure how to test that easily...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Due to the lack of lockfile, a clean install resulted in dependencies that caused the tests to fail. This commit is a vain attempt to lock down dependencies (or at least the direct ones).
55eec95
to
49e8e9a
Compare
@@ -79,7 +79,7 @@ | |||
"ts-loader": "^0.6.0", | |||
"tslint": "^4.1.1", | |||
"tslint-eslint-rules": "^3.1.0", | |||
"typescript": "^2.0.2", | |||
"typescript": "2.1.x", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have to upgrade TS in a separate PR.
Just ran into this issue today. Would love to use it. Any idea on the timeline for the next release cut? |
released
…On Wed, Mar 8, 2017 at 8:27 AM, Andrew Smith ***@***.***> wrote:
Just ran into this issue today. Would love to use it. Any idea on the
timeline for the next release cut?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#659 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAG1T1JPU-aM8tAQ4s4FOALIA04YYBgWks5rjtbtgaJpZM4MSF_2>
.
|
Many Thanks!
… On Mar 12, 2017, at 1:00 PM, Miško Hevery ***@***.***> wrote:
released
On Wed, Mar 8, 2017 at 8:27 AM, Andrew Smith ***@***.***>
wrote:
> Just ran into this issue today. Would love to use it. Any idea on the
> timeline for the next release cut?
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#659 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAG1T1JPU-aM8tAQ4s4FOALIA04YYBgWks5rjtbtgaJpZM4MSF_2>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
No description provided.