-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EP-149] Rename Properties (Phase One) #1370
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1370 +/- ##
==========================================
+ Coverage 85.83% 85.85% +0.01%
==========================================
Files 1100 1100
Lines 95932 95971 +39
==========================================
+ Hits 82347 82394 +47
+ Misses 13585 13577 -8
Continue to review full report at Codecov.
|
Library/Tracking/KSRAnalytics.swift
Outdated
result["reward_id"] = data.rewardId | ||
result["reward_title"] = data.rewardTitle | ||
result["reward_is_limited_quantity"] = reward.limit != nil |
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.
Are we using this logic anywhere else in the app? What do you think about making a computed property on the Reward model?
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.
Ah good catch. It looks like we are using this same logic for this property and the one below it in another file as well. Changed to a computed property and replaced in a few places.
馃摬 What
As part of our ongoing initiative to implement
Segment
and replace our legacy tracking clients, we begin here with some renaming of old events. The Insights team has provided us with a set of properties and the contexts they belong to; this PR is one of many upcoming extensions to the addition of Segment.馃 Why
Our events and their respective tracking clients are present everywhere in this project. It's important that we break down all these tasks into manageable bits. Each phase of work will be represented by anywhere from one to three tickets.
馃洜 How
A lot of the work is in our
KSRAnalytics
file and the tests that make use of it.