-
Notifications
You must be signed in to change notification settings - Fork 134
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
Merge v2 to develop
#1050
Merge v2 to develop
#1050
Conversation
…k`'s value atomic
…vider RUMM-2299 Core Context Provider
…r-info-publisher RUMM-2299 Core Context User Info Publisher
…nch-time-reader RUMM-2299 Core Context Launch Time Reader
…-state-publisher RUMM-2299 Core Context Application State Publisher
# Conflicts: # Datadog/Datadog.xcodeproj/project.pbxproj
…equest-builder RUMM-2207 Delegate building HTTP request to features
…eader RUMM-2207 Battery Status Reader and Low Battery Mode Publisher
# Conflicts: # Datadog/Datadog.xcodeproj/project.pbxproj # Tests/DatadogTests/Datadog/Core/System/Time/DateCorrectionTests.swift
…-context RUMM-2334 Tracing with RUM Through Core Context
Co-Authored-By: Maciek Grzybowski <maciek.grzybowski@datadoghq.com>
RUMM-2603 Create V2 Registration Interfaces
…publisher RUMM-2606 Battery Status Publisher
Co-Authored-By: Maciek Grzybowski <maciek.grzybowski@datadoghq.com>
Co-authored-by: Maciek Grzybowski <maciek.grzybowski@datadoghq.com>
…lisher RUMM-2606 Launch Time Publisher
…lisher RUMM-2381 Add internal proxy API for customising app version
Datadog ReportBranch report: ✅ |
# Conflicts: # Sources/Datadog/Core/FeaturesConfiguration.swift # Tests/DatadogTests/Datadog/Mocks/CoreMocks.swift
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.
Looks OK 👍. Because of the size of this PR: do you think there are there particular things we may want to look at @maxep? I double checked the "merge branch develop
" commits that annotate conflicted files and the last "fix merge conflict" change - it's all fine 👍 + the work from conflicted PRs seems good as well.
On top of human review, I think we must rely on tests 🤖 for ultimate qualification. I see that all were included 👍👌, so it's good to go for me.
The only things are the conflicts I mentioned. The most impactful was tackled and reviewed in #1048 👍
|
What and why?
merge v2 progress in
develop
branch.Conflicts
The following PRs were conflicting with
v2
:version
#973@fuzzybinary could you please double check?
Review checklist
Custom CI job configuration (optional)