As a user, I want the ability to add configuration options during initialization, catering to both migrating users and new adopters of the packafe. This involves using updated configurations in the initialization method, allowing the end user to easily adjust configs in their app. For migrating users, while migrationSiteId is optional, it is expected for those transitioning from Journeys to CDP. If migrationSiteId is not provided, the SDK will assume no migration is needed, treating the user as a new CDP user, and any unprocessed tasks will not be handled.
Exlcusions
Sample app updates
Initializing the package as the flow is broken at the moment
Using iOS or Android CDP SDK
Solution
This PR updates the configurations as per the tech proposal and consumes in current initialization method.
Testing
The current flow of the modules is broken, and the ticket does not include updates to the sample app, making testing of the changes not possible at this time. Testing will be carried out at the end of this milestone, consolidated into a single branch and PR.
Linear: https://linear.app/customerio/issue/MBL-443/update-package-configuration-for-initialization
Problem
As a user, I want the ability to add configuration options during initialization, catering to both migrating users and new adopters of the packafe. This involves using updated configurations in the initialization method, allowing the end user to easily adjust configs in their app. For migrating users, while
migrationSiteIdis optional, it is expected for those transitioning from Journeys to CDP. IfmigrationSiteIdis not provided, the SDK will assume no migration is needed, treating the user as a new CDP user, and any unprocessed tasks will not be handled.Exlcusions
Using iOS or Android CDP SDK
Solution
This PR updates the configurations as per the tech proposal and consumes in current initialization method.
Testing
The current flow of the modules is broken, and the ticket does not include updates to the sample app, making testing of the changes not possible at this time. Testing will be carried out at the end of this milestone, consolidated into a single branch and PR.