-
Notifications
You must be signed in to change notification settings - Fork 66
included evaluated_at properties in $feature_flag_called events
#394
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
Conversation
ioannisj
left a comment
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.
LG, but we need to implement storage.getInt() & storage.setInt() cause builds are failing
evaluated_at properties in $feature_flag_called events
ioannisj
left a comment
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.
LG, just a minor question for clarification
PostHog/PostHogStorage.swift
Outdated
| } else if let dictValue = value as? [String: Any] { | ||
| if let intValue = dictValue[key.rawValue] as? Int { | ||
| return intValue | ||
| } else if let numberValue = dictValue[key.rawValue] as? NSNumber { | ||
| return numberValue.intValue | ||
| } | ||
| } |
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.
Do we need this fallback logic on nested dictionary values with same keys, or can we simplify?
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.
oh yeah, this is kinda gross. I'll make it better.
|
|
||
| - feat: include `evaluated_at` properties in `$feature_flag_called` events ([#394](https://github.com/PostHog/posthog-ios/pull/394)) | ||
|
|
||
| ## 3.36.0 - 2025-12-03 |
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 wasnt released yet (under next), so wrong versioning and wrong date
| @@ -1,5 +1,11 @@ | |||
| ## Next | |||
|
|
|||
| ## 3.37.0 - 2025-12-08 | |||
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.
.36 and .37 ahould be .36 since its not released yet, both the date of the release, today?
💡 Motivation and Context
See PostHog/posthog#41824 for context
💚 How did you test it?
New unit tests
📝 Checklist