-
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
Dogfood recent changes #1136
Dogfood recent changes #1136
Conversation
Hotfix 1.12.1
Release 1.13.0
This reverts commit ead0f4b.
Downgrade to version 2.1.3 of testing framework
Co-Authored-By: Maciek Grzybowski <maciek.grzybowski@datadoghq.com>
…h-data-to-pointer-interaction-model RUMM-2784 [SR] Migrate to `PointerInteractionData` for sending touch information
…sure Replace `CodableValue` with `AnyCodable`
RUMM 2817 TLV Telemetry
…emock-sharing RUMM-2690 PassthroughContextMock sharing with Session Replay package
RUMM-2902 [SR] Add `DatadogSDKSessionReplay.podspec`
Fix develop build issues
- to reflect the lowest supported Xcode version (13.0)
Align `swift-tools-version` across all packages
Datadog ReportBranch report: ✅ |
3d2c360
to
6abed76
Compare
- SR cannot use main `Package.swift` because it includes another definition of `DatadogSessionReplay`.
swiftSettings: [ | ||
.define("SPM_BUILD"), | ||
.define("DD_SDK_ENABLE_EXPERIMENTAL_APIS"), | ||
] |
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.
It is not possible to add path: ..
as SPM will complain that sources cannot be located in outside of package directory. Symbolic links to Sources
and Tests
workaround this limit.
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.
I don't believe any of this affects the public docs, so there's nothing for docs to review.
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.
🚀 🐶
What and why?
🐶 Merging
develop
intodogfooding
, so the SDK version will be upgraded in mobile app and Shopist.DatadogCoreProxy
in tests #1111PointerInteractionData
for sending touch information #1087How?
Following recent change on
develop
, I updated the location of SR module in dogfoodedPackage.swift
.Because we're in the middle of V2 migration and
DatadogInternal
module is not yet available as stand-alone package that SR could depend on, that change ☝️ broke our SR unit tests setup. Xcode was confused with resolving following:DatadogSessionReplay/Package.swift
defining its ownDatadogSessionReplay
moduleDatadogSessionReplay/Package.swift
linking to../Package.swift
which also definesDatadogSessionReplay
DatadogSessionReplay/Package.swift
linking to../TestUtilities/Package.swift
which links../Package.swift
that definesDatadogSessionReplay
To avoid this confusion, this PR adds
DDPatchForSR/Package.swift
which is basically a copy of the mainPackage.swift
available ondevelop
. Unlike the mainPackage.swift
ondogfooding
branch, it makes no mention ofDatadogSessionReplay
module.That approach seeks at introducing minimal change (it will be erased once we reach V2):
bitrise.yml
madeDatadogSessionReplay/Package.swift
and/TestUtilities/Package.swift
that should not conflict withdevelop
changes any time soonTo make
DDPatchForSR/Package.swift
work without introducing any changes in repository layout, two symbolic links were created:DDPatchForSR/Sources
→/Sources
DDPatchForSR/Tests
→/Tests
Entire patch is done in this commit: c374b78
Other than this, just
develop
→dogfooding
merge.Review checklist
Custom CI job configuration (optional)