docs: add CNAME initialization examples for iOS and Android#87
Conversation
PR SummaryLow Risk Overview The README gains optional snippets after the existing iOS and Android init examples: Swift and Objective-C set Reviewed by Cursor Bugbot for commit 50e1573. Bugbot is set up for automated code reviews on this repo. Configure here. |
Cordova consumers initialise the mParticle SDK natively from their AppDelegate / Application class, so a custom CNAME endpoint is configured the same way as in any non-Cordova app — via `MPNetworkOptions.customBaseURL` on iOS or `NetworkOptions.withNetworkOptions` on Android. No JS bridge needed. Mirrors the docs portion of mParticle/mparticle-flutter-sdk#73. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
53c6af4 to
50e1573
Compare
|
Docs only change, so build/test failure is not an issue - this should be fixed in shoppable-ads branch. |
Background
mParticle Flutter PR #73 added README examples for configuring a custom CNAME endpoint without any new Dart API — Flutter consumers initialise the mParticle SDK natively from their
AppDelegate/Applicationclass and wireMPNetworkOptions.customBaseURL/NetworkOptions.withNetworkOptionsdirectly. React Native takes the same approach (no runtime JS bridge; only an Expo config plugin for build-time codegen). Cordova consumers initialise the same way, so a docs-only change matches.What's changed
MPNetworkOptions.customBaseURLsnippet (Swift + Objective-C) inserted after the standard init example.NetworkOptions.withNetworkOptionssnippet (Java + Kotlin) inserted after the standard init example.CHANGELOG.md[Unreleased]entry under Added.No JS API, no native bridge changes, no dependency bumps.
🤖 Generated with Claude Code