Skip to content

fix(eventtagsutils) : don't exclude falsy values #132

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

Merged
merged 2 commits into from
Jan 28, 2019

Conversation

msohailhussain
Copy link
Contributor

Summary

0 and 1 after deserialization converted into long and we were not considering long in the numeric method. just added it. Along with I realized to add short/uint as well.
The "why", or other context.

Test plan

Issues

Copy link
Contributor

@mikeproeng37 mikeproeng37 left a comment

Choose a reason for hiding this comment

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

lgtm, just have some small suggestions

@@ -970,6 +970,183 @@ public void TestConversionEventWithNumericTag()
Assert.IsTrue(TestData.CompareObjects(expectedEvent, logEvent));
}

[Test]
public void TestConversionEventWithFalsyValues()
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: with falsy numeric and revenue values

}

[Test]
public void TestConversionEventWithNumericValue1()
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: maybe we should check revenue and event value in separate tests

@mikeproeng37 mikeproeng37 merged commit dc860a9 into master Jan 28, 2019
@msohailhussain msohailhussain deleted the sohail/fixnumer0and1 branch January 31, 2019 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants