-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Enable no implicit any in the utilities package #1970
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
Changes from 2 commits
6859401
3ba6c92
22a9202
3265787
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,10 @@ | ||
| import { memoize, memoizeFunction, setMemoizeWeakMap } from './memoize'; | ||
| import * as weakMapPolyfill from 'es6-weak-map/polyfill'; | ||
| import weakMapPolyfill = require('es6-weak-map'); | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I made a fix to be ok with WeakMap missing in the |
||
|
|
||
| let { expect } = chai; | ||
|
|
||
| describe('memoizeFunction', () => { | ||
| before(()=> { | ||
| before(() => { | ||
| setMemoizeWeakMap(weakMapPolyfill); | ||
| }); | ||
|
|
||
|
|
@@ -95,7 +95,7 @@ describe('memoizeFunction', () => { | |
| }); | ||
|
|
||
| describe('memoize', () => { | ||
| before(()=> { | ||
| before(() => { | ||
| setMemoizeWeakMap(weakMapPolyfill); | ||
| }); | ||
|
|
||
|
|
||
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.
Seems like there is a bug here, but I don't have enough context. Id is a string since it's a key in _timeoutIds, but it's being used as a number...
Uh oh!
There was an error while loading. Please reload this page.
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 don't think that's a bug, unless it's browser specific. I just tried it by caching the stringified value of the response of setTimeout and then calling clearTimeout with it and it worked. Are you seeing an actual bug?
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 am not seeing an actual bug. It just stood out to me.