-
Notifications
You must be signed in to change notification settings - Fork 3k
chore(test): fix scheduler and subject types #3748
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
Conversation
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.
@@ -71,11 +71,11 @@ describe('Scheduler.asap', () => { | |||
const fakeTimer = sandbox.useFakeTimers(); | |||
// callThrough is missing from the declarations installed by the typings tool in stable | |||
const stubSetInterval = (<any> sinon.stub(global, 'setInterval')).callThrough(); | |||
function dispatch(state: any): void { | |||
function dispatch(this: any, state: any): void { |
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.
I'd love a second pass that removes some of the any
types that are being added, but that shouldn't block the PR.
Waiting to see if @kwonoj can restart the build. |
@david-driscoll I can probably get rid of some of those this-parameter anys pretty quickly with judicious use of |
retriggered build. |
@david-driscoll Used appropriate types instead of |
Description:
Continues from PR #3680 and fixes tests for schedulers and subjects.
This should be the last of the fixes.
After this is merged, I'll remove the
test_check
script and will changetest
to include type checking. I'll also create atest_fast
script - which will be the same astest
, but without the type checking - for use with watched builds, etc., as I suspect the type checking will take several seconds.Related issue (if exists): #3411 #3680