feat(RN): Add wiring for protocol events - add ec.start

[kieran-osgood-shopify]

What changes are you making?

Part of the scope of this PR is to add a translation layer between the the core native SDKs and the React native JavaScript runtime. The models that are generated for Swift and Kotlin in automatically camel case at their encode decode boundary, which means the raw Jason is read as snake case and the Swift and Kotlin properties are then turned into camel case when they are turned back into raw Jason, they're back in Snakecase.

This is problematic for React Native because we do not have a schema validation library. we are just using the CodeGen TypeScript interfaces, faces which again are in camel case which means we need some layer to convert that over to camelCase.

I consider doing this on the TypeScript level

• This would require greater degrees of unsafe mapping due to the types at play
• I also didn't want to be blocking the main thread with lots of IO intensive work.

How to test

---

Before you merge

Important

• I've added tests to support my implementation
• I have read and agree with the Contribution Guidelines
• I have read and agree with the Code of Conduct
• I've updated the relevant platform README (platforms/swift/README.md and/or platforms/android/README.md)

---

Releasing a new Swift version?

• I have bumped the version in ShopifyCheckoutKit.podspec
• I have bumped the version in platforms/swift/Sources/ShopifyCheckoutKit/ShopifyCheckoutKit.swift
• I have updated platforms/swift/CHANGELOG.md
• I have updated the SwiftPM/CocoaPods version snippets in platforms/swift/README.md (major version only)

Releasing a new Android version?

• I have bumped the versionName in platforms/android/lib/build.gradle
• I have updated platforms/android/CHANGELOG.md
• I have updated the Gradle/Maven version snippets in platforms/android/README.md

Tip

See the Contributing documentation for the full release process per platform.

[kieran-osgood-shopify]

• feat(RN): Include remaining public protocol events from native #186
• feat(RN): Wire up accelerated checkouts with protocol events #181
• feat(RN): Add wiring for protocol events - add ec.start  #170 👈 (View in Graphite)
• feat(RN): replace addEventListener with callback args #119 : 2 other dependent PRs (#125 , #134 )
• feat(react-native): use local android/swift project references #115 : 1 other dependent PR (#116 )
• feat(protocol): add typescript interfaces #114
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

React Native — Coverage Report

Lines	Statements	Branches	Functions
	96.36% (265/275)	91.37% (159/174)	100% (70/70)

[kieran-osgood-shopify]

Need to improve the API here - seems like we might need a mapping layer, otherwise this unfortunately gives autocomplete of 'ec.start'

[kiftio]

AI feedback, so unsure of accuracy

 The RN pod target does not define COCOAPODS in OTHER_SWIFT_FLAGS, so CocoaPods builds will take the #else branch and try to import ShopifyCheckoutProtocol, which is not a pod/module dependency. If we fix that by adding -DCOCOAPODS, CheckoutProtocolBridge.swift then appears to redeclare the conformance already provided by ShopifyCheckoutKit in platforms/swift/Sources/ShopifyCheckoutKit/CheckoutCommunicationProtocol.swift:33. I’d key this on SWIFT_PACKAGE instead and delete the retroactive conformance.

[kiftio]

AI also came up with one thing here..

transformKeys rewrites every dictionary key, including map keys that are data rather than field names. UCP registries like payment_handlers, services, and capabilities are keyed by reverse-domain names, and those keys can contain underscores. A key like com.example.loyalty_gold would become com.example.loyaltyGold before JS sees it. The casing pass should avoid transforming dynamic registry/map keys, or use a schema-aware/generated serializer.

The example it gave

  {
    "ucp": {
      "payment_handlers": {
        "com.example.loyalty_gold": []
      }
    }
  }

The desired JS shape is:

  {
    "ucp": {
      "paymentHandlers": {
        "com.example.loyalty_gold": []
      }
    }
  }

But the current recursive transform would produce:

  {
    "ucp": {
      "paymentHandlers": {
        "com.example.loyaltyGold": []
      }
    }
  }

Do we need to be concerned with this?

[kieran-osgood-shopify]

Honestly good question - I hadn't considered this, I'll look into it