@chipmobilesdk/rn-payment 0.5.0 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,177 @@
 # @chipmobilesdk/rn-payment
 
+## 0.7.0
+
+### Minor Changes
+
+- Every package now ships built JavaScript with declaration files, instead of asking the
+  app to compile its TypeScript. ([#22](https://github.com/operationd8979/chip-mobile-sdk/pull/22))
+
+  Each tarball carries `lib/commonjs`, `lib/module` and `lib/typescript` (built with
+  `react-native-builder-bob`), and `src/` alongside them. What that changes for a
+  consumer:
+
+  - **Nothing to add to `transformIgnorePatterns`.** `require` resolves to the CommonJS
+    build, so an app's Jest loads this package without being told to transform it. That
+    was the one thing every consuming app had to know about us (DEP-04).
+  - **Typechecking reads our `.d.ts`** rather than compiling our source under our
+    `tsconfig`. A consumer's stricter — or looser — settings no longer meet our code.
+  - **`import` resolves to ESM**, so a bundler can tree-shake what it does not use.
+
+  No exported name changed, and no subpath moved: `.`, `./testing`, `./push`,
+  `./advanced`, `./app-auth`, `./keychain` and rn-core's twelve subpaths resolve exactly
+  as before, each now with its own declarations for both module systems. publint and
+  `attw --profile node16` pass on all twelve packages, which they could not before.
+
+  Inside the monorepo nothing changed either, and that is deliberate: every subpath also
+  declares a private `chipmobilesdk-source` condition pointing at its TypeScript, and
+  Metro, Jest and `tsc` here ask for that condition first. The demo app bundles 371
+  modules straight from `packages/*/src`, so editing a package still changes the app with
+  no build step, and coverage is still measured on the source. The condition is named for
+  this organization rather than using the conventional `source` because third-party
+  packages declare that one too — `@dr.pogodin/react-native-fs` does — and asking for it
+  pulled their sources into our stricter compile.
+
+  `npm run build:packages` builds everything, `prepack` rebuilds before any `npm pack`,
+  and `lib/` is git-ignored: the published bytes are produced by the release, never
+  committed. `npm run check:manifests` now fails a package whose `main`, `module`,
+  `types`, `source` condition, `files`, build script or `prepack` do not match this shape.
+
+### Patch Changes
+
+- Every peer range has an upper bound, and no package declares a peer it does not use. ([#21](https://github.com/operationd8979/chip-mobile-sdk/pull/21))
+
+  A peer range is now a caret, a tilde or an explicit `<`, except for `react` and
+  `react-native`: an app brings exactly one of each, so a floor is the only useful thing
+  to say about them. Every other peer is a library the app installs beside us, and an
+  open `>=` was a promise about versions nobody had run — mmkv 3→4 lost entitlements and
+  pending purchases exactly that way.
+
+  **Four of the new ceilings exclude a version that is already published**, so an app
+  that took the open range at its word may now see a peer warning. The new bound is the
+  major this release is tested against, which is the thing the old range failed to say:
+
+  | Peer | Was | Now | Published above the ceiling |
+  |---|---|---|---|
+  | `react-native-app-auth` (rn-auth) | `>=8` | `^8.0.0` | 9.0.0 |
+  | `react-native-keychain` (rn-auth) | `>=10` | `^10.0.0` | 11.0.0 |
+  | `@op-engineering/op-sqlite` (rn-local-db) | `>=17.1.0` | `^17.1.0` | 18.x, 19.x |
+  | `@react-native-firebase/messaging` (rn-notification) | `>=26.0.0` | `^26.0.0` | 27.x |
+
+  The others — `react-native-vision-camera` `^5.1.1`, `react-native-svg` `^15.15.0`,
+  `react-native-unistyles` `^3.2.0`, `@dr.pogodin/react-native-fs` `^2.39.2`,
+  `react-native-quick-crypto` `^1.0.0`, `react-native-notify-kit` `^10.5.0`,
+  `react-native-localize` `^3.7.0`, `react-native-mmkv` `^4.0.0` — exclude nothing that
+  exists today. rn-payment's mmkv range was already bounded (`>=4.0.0 <5`) and is now
+  written as the caret that means the same thing.
+
+  Peers nothing imports are gone. `rn-theme`, `rn-local-db` and `rn-notification` asked
+  for `react` without having a component or a hook between them; `rn-auth`, `rn-ai` and
+  `rn-i18n` asked for `react-native` without touching a React Native API (rn-auth reaches
+  both native modules through `lazyPeer`, rn-i18n formats on `Intl`); `rn-notification`
+  asked for `@react-native-firebase/app`, which messaging declares itself. `rn-ai` no
+  longer peers on `@chipmobilesdk/rn-auth` at all — it asks for a `TokenProvider`, a
+  two-method interface rn-auth's `auth` satisfies, so an app with its own token source
+  installs nothing extra. An app that enables push or signs in through rn-auth installs
+  the same packages as before; it is the manifest that stopped overstating.
+
+  `react-native-localize` is declared optional, which is what the code already did: the
+  time-zone reader goes through `lazyPeer` and falls back to `Intl` without it. The
+  `peerDependenciesMeta` entries that said `optional: false` are gone — that is npm's
+  default, and writing it down only invited the question of which peers were undecided.
+
+  `npm run check:manifests` now fails on an unbounded peer range, a peer nothing in
+  `src/` imports, and a `peerDependenciesMeta` entry for either, so the policy holds
+  without anyone remembering it.
+
+- Each package's public API and its weight are now recorded in the repository, so a change
+  to either is reviewed rather than discovered. ([#23](https://github.com/operationd8979/chip-mobile-sdk/pull/23))
+
+  `packages/<pkg>/etc/*.api.md` is an api-extractor report per entrypoint — twenty-seven
+  of them, generated from the declarations the package publishes and committed. A renamed
+  type, a widened union, one more optional field: all of it shows up in a pull request's
+  diff. `npm run check:api` fails when a report is out of date and `npm run api:update`
+  rewrites them.
+
+  A report that moves now needs a **minor or major** changeset for that package.
+  `check:changesets` enforces it, because the report is generated from what the package
+  publishes, and a patch release that moves the public surface is how a consumer's build
+  breaks on `npm update`. A report added for the first time is a baseline, not a change.
+  `./testing` deliberately has no report: test doubles are not a surface a release is
+  gated on.
+
+  `npm run check:size` holds every entrypoint to a budget in `.size-limit.json`, measured
+  on the ESM build with peers and rn-core treated as external — they are what an app
+  installs beside us, not our weight. Each budget started at today's measurement plus five
+  per cent, so growth becomes a decision someone makes instead of a drift nobody sees. The
+  current figures run from 500 B (`rn-core/lazy`) to 19 kB (rn-notification).
+
+  No behaviour or API changed in this release; the entry is here so the changelog records
+  when the reports and the budgets began.
+- Updated dependencies ([#22](https://github.com/operationd8979/chip-mobile-sdk/pull/22), [#23](https://github.com/operationd8979/chip-mobile-sdk/pull/23)):
+  - @chipmobilesdk/rn-core@0.2.0
+
+## 0.6.0
+
+### Minor Changes
+
+- The engine is split by responsibility, and its internals are off the public type. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+  - `PaymentEngine` no longer has `resolvedConfig`, `nextCorrelationId`, `emitter`,
+    `snapshot`, `commitSnapshot`, `mayCreateRealTransaction` or `recordBlockedOperation`.
+    They were documented as internal, but any consumer could call `commitSnapshot` and
+    grant itself an entitlement the store never sold, and a hand-written engine double had
+    to implement all of them.
+  - `entitlement_revoked` now carries the real reason: `validation_rejected` when your
+    backend said no, `consumed` for a consumed item, `expired` for a lapsed subscription,
+    and `revoked_by_store` only when the store stopped reporting the purchase. Before, every
+    revocation said `revoked_by_store`.
+  - `clearLocalData()` also drops cached product prices.
+  - A `not_ready` purchase result reports the engine's actual status instead of always
+    `connecting`. `usePurchase().purchase` takes a `ProductKey`, as it always accepted.
+  - Local storage moves to schema version 2: the never-written `entitlements` map and
+    `finalized` purchase state are gone. A version 1 record is migrated in place on first
+    load, so nothing needs to be done.
+  - Internally, `engine.ts` is 346 lines (was 921): state, connection and sync are their
+    own modules, and sync and the purchase flow build purchase records with one function.
+    The unused `runWithRetry`, `backoffSchedule`, `sourcesFor` and `entitlementsCoveredBy`
+    helpers are gone.
+
+- The provider keeps one engine, stored records are checked one by one, and product
+  queries run in parallel. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+  - `PaymentProvider` builds its engine once and keeps it across renders. Inline
+    `config` and `deps` objects no longer reconnect to the store on every render of your
+    root. A new engine is built only when the new `engineKey` prop changes (default:
+    `config.scopeToken`). It now works under React StrictMode, where it used to be left
+    holding a cleaned-up engine that never became ready. Pass `engine` to share an engine
+    you created and own; the provider then neither initializes nor cleans it up.
+  - `initialize()` on a cleaned-up engine reports `PAYMENT_NOT_CONFIGURED` even if the
+    engine had been ready, instead of answering `ok`.
+  - Every stored purchase record is checked field by field when read. A damaged one is
+    dropped and comes back with the next sync, rather than being trusted or taking the
+    rest down with it. Only a `purchased` record grants an entitlement; a state this
+    version does not know never does.
+  - A failed write to local storage is reported as an `internal_error` with
+    `PAYMENT_STORAGE_UNAVAILABLE` and operation `persist`, instead of being swallowed.
+    A custom `SnapshotStore.save` may return `false` to report one.
+  - One-time and subscription products are queried in parallel, identical requests in
+    flight share one store call, and `useProducts` never lets an older answer overwrite a
+    newer one. `status.blockedOperations` keeps the 20 most recent.
+
+- `allowStoreTestPurchases` lets a debug build buy through the real store for Play
+  license testers. It is accepted only with `environment: 'test'`; any other environment
+  rejects it at startup with `PAYMENT_INVALID_CONFIG`. Without it, non-production
+  purchases are still refused as `environment_blocked`, as before. The README no longer
+  says the billing library is uninstalled or the adapter unverified, and describes what
+  adding iOS actually involves. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+### Patch Changes
+
+- Internal: no module in these packages is over 500 lines any more. The camera controller's session I/O moved to `sessionRuntime` and its contract to `contract.ts`; the Play adapter's shape translation to `iapShapes`; the purchase flow's failure mapping and its receipt-validation hook to modules of their own; the AI client's quota request to `quotaRequest`; the in-memory adapter's attachments and the fake ads engine's clock likewise. Behaviour is unchanged — the splits are by responsibility, and every package's suite passes as it stood. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+  The repository also measures what it promised: `npm run perf` prints the median of nine runs of the deterministic hot paths against written budgets (recurrence expansion, theme construction, translation lookup, chart geometry, filter compilation), the demo app has a Performance screen reporting startup phases, time to interactive and the same benchmarks on Hermes, and `npm run check:file-size` keeps the limit from drifting. The budgets and the measured figures are recorded in `docs/standards.md` §VI.
+
 ## 0.5.0
 
 ### Minor Changes

package/README.md

@@ -91,12 +91,9 @@ npm install react-native-iap react-native-mmkv react-native-nitro-modules
 > do **not** add it yourself. No runtime permission is requested and no sensitive
 > API is touched, so there is no permission prompt and no denial path to handle.
 >
-> **Verified state in this repository:** the app manifest at
-> `android/app/src/main/AndroidManifest.xml` declares `INTERNET`, `CAMERA`, and
-> notification permissions, and **no** `BILLING` entry — correct, because the
-> billing library is not installed yet. Once it is, confirm the merged manifest
-> contains exactly one `com.android.vending.BILLING` entry and no new runtime
-> permission:
+> **Check your merged manifest** once `react-native-iap` is installed: it should
+> contain exactly one `com.android.vending.BILLING` entry, added by the billing
+> library, and no new runtime permission:
 >
 > ```bash
 > # After a debug build, inspect the merge report:
@@ -118,7 +115,7 @@ Verified against this repository's toolchain, not assumed:
 | Android `minSdk` / `compileSdk` / `targetSdk` | 24 / 36 / 36 |
 | Kotlin | 2.1.20 |
 | `react-native-iap` | >= 16.7.3 < 17 (verified 16.7.3) |
-| `react-native-mmkv` | >= 4.0.0 < 5 (the store uses v4's `createMMKV`) |
+| `react-native-mmkv` | `^4.0.0` (the store uses v4's `createMMKV`) |
 | `react-native-nitro-modules` | as required by `react-native-iap` (not a peer of this package) |
 
 **Why the `react-native-iap` ceiling is the next major.** Both the Nitro peer
@@ -164,9 +161,13 @@ const config = {
   isProductionBuild: true,
 };
 
+// Created once, outside the component: the store adapter holds the billing
+// connection.
+const deps = { provider: createStoreProvider() };
+
 export function App() {
   return (
-    <PaymentProvider config={config} deps={{ provider: createStoreProvider() }}>
+    <PaymentProvider config={config} deps={deps}>
       <YourApp />
     </PaymentProvider>
   );
@@ -182,6 +183,13 @@ function AdSlot() {
 }
 ```
 
+The provider builds its engine once and keeps it across renders; `config` and `deps`
+are read when it is built. It builds a new one when `engineKey` changes (by default
+`config.scopeToken`, so switching accounts gets a fresh engine), and it survives React
+StrictMode in development. To own the engine yourself — create it at startup, share it
+with code outside React — pass it instead: `<PaymentProvider engine={engine}>`. The
+provider then neither initializes nor cleans it up.
+
 `createStoreProvider()` picks the platform adapter. On a platform with no adapter
 it returns a stub that reports `unavailable` instead of throwing, so your app
 still starts and runs — it only loses the ability to sell.
@@ -551,6 +559,20 @@ Two layers:
    recorded in `getStatus().blockedOperations`, and emitted as
    `environment_blocked` — observable in state, so a test can assert it rather
    than scraping logs.
+3. **License testing, opted in.** `environment: 'test'` with
+   `allowStoreTestPurchases: true` lets a debug build buy through the real store,
+   so a Play license tester can check a purchase without a release build from a
+   track. Any other environment rejects the option at construction. License
+   testers are not charged; anyone else signed in on the device would be.
+
+```ts
+const config = {
+  // ...
+  environment: 'test',
+  isProductionBuild: false,
+  allowStoreTestPurchases: true, // license testers only
+};
+```
 
 > **Why this blocks where `@chipmobilesdk/rn-ads` substitutes.** The ads package
 > swaps in Google's official *test ad units* when a non-production build supplies
@@ -751,10 +773,8 @@ Exhaustively, for your Data safety declaration:
 
 | Stored | Why |
 |---|---|
-| Entitlement keys and their states | So entitlements are readable offline |
-| Granting product keys | So you can show the current plan |
-| Subscription expiry and renewal status | So lifecycle is readable offline |
-| Unfinished-transaction records (transaction id, product key, token, attempt count) | So a paid purchase is never lost to an app kill |
+| Purchase records (transaction id, product key, product type, token, purchase time, store state, finalize state and attempt count, backend validation state) | So entitlements are readable offline and a paid purchase is never lost to an app kill. Entitlements themselves are derived from these, never stored |
+| Subscription expiry and renewal status, on the purchase record | So lifecycle is readable offline |
 | Pending-purchase records (the same fields, plus the time the store reports the purchase was made) | So a payment still in flight is visible after an app kill. Unchanged since `0.1.0`; `0.2.0` only reads them |
 | Last successful sync time | So data age is observable |
 | Schema version | So the record can be migrated |
@@ -845,9 +865,11 @@ Your obligations as the app owner — this package cannot discharge them for you
    non-default policy needs server data.
 2. **iOS is contract-only.** `createStoreProvider()` returns an `unavailable` stub
    on iOS; the host app still starts and runs.
-3. **The Android adapter is unverified on a device.** Only its purchase-state
-   mapping has been checked against an installed binding. See
-   [Compatibility](#compatibility).
+3. **Debug builds do not reach the store unless you opt in.** Outside production a
+   purchase reports `environment_blocked`. For a license tester on a debug build,
+   set `environment: 'test'` and `allowStoreTestPurchases: true`; only license
+   testers are not charged. See [Compatibility](#compatibility) for the devices and
+   binding the Android adapter was verified with.
 4. **Price-change confirmation is unsupported on Android.** Play notifies the user
    itself and offers no client-side flow, so `confirmPriceChange` reports
    `unsupported` rather than faking a confirmation.
@@ -863,7 +885,12 @@ Your obligations as the app owner — this package cannot discharge them for you
 
 ## Adding iOS later
 
-Implement `ProviderPort` for StoreKit. Nothing else changes.
+Implement `ProviderPort` for StoreKit and return it from `createStoreProvider()` on
+iOS. Your entitlement checks, hooks and purchase calls do not change. What an iOS
+release adds: `storeProductIds.ios` in each catalog entry, the adapter's own
+`capabilities()` (StoreKit can tell grace period from account hold, and supports
+externally initiated purchases, so some states Android reports as `indeterminate`
+become distinct), and its conformance run (`runProviderPortConformance`).
 
 | Play concept | Port concept | StoreKit |
 |---|---|---|
@@ -890,6 +917,10 @@ Local storage carries a schema version and a forward migration chain. A record
 that cannot be migrated is discarded and rebuilt from the store — safe, because
 discarding yields `unknown`, never a false `not_entitled`.
 
+Schema version 2 (0.6.0) drops two things version 1 stored and never used: an
+empty `entitlements` map and a `finalized` purchase state nothing set. A version 1
+record is migrated in place on first load.
+
 ### Migrating `0.1.0` to `0.2.0`
 
 **One union gained a member**, so an exhaustive `switch` over it needs the new

package/lib/commonjs/adapter/createStoreProvider.js

@@ -0,0 +1,110 @@
+"use strict";
+
+Object.defineProperty(exports, "__esModule", {
+  value: true
+});
+exports.createStoreProvider = createStoreProvider;
+exports.createUnsupportedProvider = createUnsupportedProvider;
+var _reactNative = require("react-native");
+var _iapAdapter = require("./iap-adapter.js");
+/**
+ * Platform selection for the store adapter.
+ *
+ * This exists so the public surface never names a store. An app writes
+ * `createStoreProvider()`, not `createIapAdapter()` — the same call will pick the
+ * StoreKit adapter once iOS exists, and no consumer line changes (FR-002, FR-004,
+ * FR-007).
+ *
+ * On a platform with no adapter the result is a stub that reports
+ * `platform_unsupported` rather than throwing. That is what lets a host app start
+ * and run normally where selling is impossible, losing only the ability to sell
+ * (FR-021, FR-023).
+ */
+
+const UNSUPPORTED_CAPABILITIES = {
+  supportsSubscriptions: false,
+  supportsPlanChange: false,
+  supportsPriceChangeConfirmation: false,
+  reportsGraceAndHoldDistinctly: false,
+  supportsExternalTransactions: false,
+  /** Nothing here can charge anyone, so the environment guard has nothing to block. */
+  createsRealTransactions: false,
+  purchaseOutcomeIncludesStoreTime: false
+};
+
+/**
+ * The no-adapter stub.
+ *
+ * Every operation fails safely and predictably. Notably `queryOwned` returns an
+ * empty list rather than throwing: the engine then computes `not_entitled` after a
+ * successful-but-empty sync, which is honest — on a platform with no store, the
+ * user genuinely holds nothing this package can verify.
+ */
+function createUnsupportedProvider() {
+  return {
+    async connect() {
+      return {
+        ok: false,
+        reason: 'platform_unsupported',
+        retryable: false
+      };
+    },
+    async disconnect() {
+      // Nothing was ever connected.
+    },
+    observeConnection() {
+      return () => undefined;
+    },
+    async queryProducts() {
+      return [];
+    },
+    async queryOwned() {
+      return [];
+    },
+    async launchPurchase() {
+      return {
+        ok: false,
+        reason: 'not_ready',
+        detail: 'platform_unsupported'
+      };
+    },
+    observePurchases() {
+      return () => undefined;
+    },
+    async acknowledge() {
+      // No transaction can exist to acknowledge.
+    },
+    async consume() {
+      // As above.
+    },
+    async openSubscriptionManagement() {
+      // No store screen to open.
+    },
+    async confirmPriceChange() {
+      return {
+        ok: false,
+        reason: 'not_ready'
+      };
+    },
+    capabilities: () => UNSUPPORTED_CAPABILITIES
+  };
+}
+/**
+ * The platform's store adapter.
+ *
+ * iOS deliberately returns the stub today rather than throwing: the contract is
+ * prepared for StoreKit, the implementation is not, and an app running on iOS
+ * should degrade to "cannot sell here" instead of crashing.
+ */
+function createStoreProvider(options = {}) {
+  if (options.forceUnsupported) {
+    return createUnsupportedProvider();
+  }
+  if (_reactNative.Platform.OS === 'android') {
+    return (0, _iapAdapter.createIapAdapter)();
+  }
+  return createUnsupportedProvider();
+}
+
+/** Exported for a test or a screen that needs the stub explicitly. */
+//# sourceMappingURL=createStoreProvider.js.map

package/lib/commonjs/adapter/createStoreProvider.js.map

@@ -0,0 +1 @@
+{"version":3,"names":["_reactNative","require","_iapAdapter","UNSUPPORTED_CAPABILITIES","supportsSubscriptions","supportsPlanChange","supportsPriceChangeConfirmation","reportsGraceAndHoldDistinctly","supportsExternalTransactions","createsRealTransactions","purchaseOutcomeIncludesStoreTime","createUnsupportedProvider","connect","ok","reason","retryable","disconnect","observeConnection","undefined","queryProducts","queryOwned","launchPurchase","detail","observePurchases","acknowledge","consume","openSubscriptionManagement","confirmPriceChange","capabilities","createStoreProvider","options","forceUnsupported","Platform","OS","createIapAdapter"],"sourceRoot":"../../../src","sources":["adapter/createStoreProvider.ts"],"mappings":";;;;;;;AAcA,IAAAA,YAAA,GAAAC,OAAA;AAEA,IAAAC,WAAA,GAAAD,OAAA;AAhBA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;;AAeA,MAAME,wBAA8C,GAAG;EACtDC,qBAAqB,EAAE,KAAK;EAC5BC,kBAAkB,EAAE,KAAK;EACzBC,+BAA+B,EAAE,KAAK;EACtCC,6BAA6B,EAAE,KAAK;EACpCC,4BAA4B,EAAE,KAAK;EACnC;EACAC,uBAAuB,EAAE,KAAK;EAC9BC,gCAAgC,EAAE;AACnC,CAAC;;AAED;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA,SAASC,yBAAyBA,CAAA,EAAiB;EAClD,OAAO;IACN,MAAMC,OAAOA,CAAA,EAAoC;MAChD,OAAO;QAAEC,EAAE,EAAE,KAAK;QAAEC,MAAM,EAAE,sBAAsB;QAAEC,SAAS,EAAE;MAAM,CAAC;IACvE,CAAC;IACD,MAAMC,UAAUA,CAAA,EAAkB;MACjC;IAAA,CACA;IACDC,iBAAiBA,CAAA,EAAgB;MAChC,OAAO,MAAMC,SAAS;IACvB,CAAC;IACD,MAAMC,aAAaA,CAAA,EAA+B;MACjD,OAAO,EAAE;IACV,CAAC;IACD,MAAMC,UAAUA,CAAA,EAAgC;MAC/C,OAAO,EAAE;IACV,CAAC;IACD,MAAMC,cAAcA,CAAA,EAAqC;MACxD,OAAO;QAAER,EAAE,EAAE,KAAK;QAAEC,MAAM,EAAE,WAAW;QAAEQ,MAAM,EAAE;MAAuB,CAAC;IAC1E,CAAC;IACDC,gBAAgBA,CAAA,EAAgB;MAC/B,OAAO,MAAML,SAAS;IACvB,CAAC;IACD,MAAMM,WAAWA,CAAA,EAAkB;MAClC;IAAA,CACA;IACD,MAAMC,OAAOA,CAAA,EAAkB;MAC9B;IAAA,CACA;IACD,MAAMC,0BAA0BA,CAAA,EAAkB;MACjD;IAAA,CACA;IACD,MAAMC,kBAAkBA,CAAA,EAAwC;MAC/D,OAAO;QAAEd,EAAE,EAAE,KAAK;QAAEC,MAAM,EAAE;MAAY,CAAC;IAC1C,CAAC;IACDc,YAAY,EAAEA,CAAA,KAAMzB;EACrB,CAAC;AACF;AAYA;AACA;AACA;AACA;AACA;AACA;AACA;AACO,SAAS0B,mBAAmBA,CAACC,OAA6B,GAAG,CAAC,CAAC,EAAgB;EACrF,IAAIA,OAAO,CAACC,gBAAgB,EAAE;IAC7B,OAAOpB,yBAAyB,CAAC,CAAC;EACnC;EACA,IAAIqB,qBAAQ,CAACC,EAAE,KAAK,SAAS,EAAE;IAC9B,OAAO,IAAAC,4BAAgB,EAAC,CAAC;EAC1B;EACA,OAAOvB,yBAAyB,CAAC,CAAC;AACnC;;AAEA","ignoreList":[]}