Skip to content

Conversation

aozgaa
Copy link
Contributor

@aozgaa aozgaa commented Jun 16, 2015

There are several places in the code that unnecessarily use == or != instead of === or !==, respectively. This makes the easy change where possible.

Changes haven't been made in a couple places that do depend on type coercions, as this breaks the baselines.

@msftclas
Copy link

Hi @aozgaa, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!


It looks like you're a Microsoft contributor (Arthur Ozga). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@aozgaa aozgaa self-assigned this Jun 16, 2015
@JsonFreeman
Copy link
Contributor

👍

aozgaa pushed a commit that referenced this pull request Jun 17, 2015
@aozgaa aozgaa merged commit 68085fc into master Jun 17, 2015
@@ -234,6 +234,7 @@ namespace ts {
public getChangeRange(oldSnapshot: IScriptSnapshot): TextChangeRange {
var oldSnapshotShim = <ScriptSnapshotShimAdapter>oldSnapshot;
var encoded = this.scriptSnapshotShim.getChangeRange(oldSnapshotShim.scriptSnapshotShim);
// TODO: should this be '==='?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. please remove comment.

@mhegazy mhegazy deleted the cleanupDoubleEquals branch June 18, 2015 07:00
@aozgaa aozgaa mentioned this pull request Apr 5, 2017
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants