-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
chore(tslint): update tslint to 4.x #13603
Conversation
This doesn't appear to work on CircleCI |
75cf30e
to
2dbc1b8
Compare
@chuckjaz PTAL |
@@ -11,7 +11,7 @@ import {NgZone} from '@angular/core'; | |||
import {global} from './facade/lang'; | |||
import {getDOM} from './private_import_platform-browser'; | |||
|
|||
export let browserDetection: BrowserDetection = new BrowserDetection(null); | |||
let browserDetection: BrowserDetection = new BrowserDetection(null); |
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.
This breaks the file because classes cannot be used before they are declared (probably worked only as a side-effect of how the export
was generated). To fix, remove the initializer as it is redundant with the the call to setup()
on line 75.
cc1bcf1
to
c676bfe
Compare
@chuckjaz PTYAL |
@@ -135,6 +135,10 @@ export function stringifyElement(el: any /** TODO #9100 */): string { | |||
return result; | |||
} | |||
|
|||
browserDetection = new BrowserDetection(null); |
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.
Why is this necessary? Line 75 contains BrowserDetection.setup();
for which setup()
is browserDetection = new BrowserDetection(null);
Why do we create two?
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
@chuck I did clone tslint, fix the issue and send a PR and then I realize I started from the wrong repo and that it was already fixed in the parent repo.
Anyway this PR should remove the bug.