-
Notifications
You must be signed in to change notification settings - Fork 131
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
timeout-service should fail on $window.setTimeout #434
Comments
@Gillespie59 now that this has been merged to development branch, when will it make it into a release ? |
I will publish the new version when this PR is finished : #432 |
It looks like it's not going to finish soon, think you can publish without
it?
…On Sun, Jan 15, 2017, 20:40 Emmanuel DEMEY ***@***.***> wrote:
I will publish the new version when this PR is finished : #432
<#432>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#434 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADN7WL0j1JNKDSBN7wKOcKaaaJ82_SX5ks5rSmgbgaJpZM4Lj2nO>
.
|
@Gillespie59 any input on this, can we push forward release of new version with #435 ? |
1.6.2 publish |
Thanks
…On Sun, Mar 5, 2017, 20:51 Emmanuel DEMEY ***@***.***> wrote:
1.6.2 publish
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#434 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADN7WJK-3xmR33fDVYmnMn7_LWsBKQqJks5riwQlgaJpZM4Lj2nO>
.
|
Right now timeout-service rule warns on
setTimeout
and onwindow.setTimeout
but it does not warn on$window.setTimeout
which is an unfortunate option as well.Planning to provide pull request with added support, please let me know if there are any objections
The text was updated successfully, but these errors were encountered: