@flopay/react 1.4.17 → 1.4.19
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +28 -0
- package/dist/index.cjs +9 -9
- package/dist/index.d.cts +1 -1
- package/dist/index.d.ts +1 -1
- package/dist/index.mjs +9 -9
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -759,6 +759,24 @@ No endpoint, custom tag, user context, message, stack, or metadata can be
|
|
|
759
759
|
configured. See [`docs/TELEMETRY.md`](../../docs/TELEMETRY.md) for the complete
|
|
760
760
|
privacy and retention contract.
|
|
761
761
|
|
|
762
|
+
If the React host has its own Sentry client, use the re-exported pure filter as
|
|
763
|
+
the host's `beforeSend` callback:
|
|
764
|
+
|
|
765
|
+
```ts
|
|
766
|
+
import * as Sentry from '@sentry/browser';
|
|
767
|
+
import { dropThirdPartyOnlyError } from '@flopay/react';
|
|
768
|
+
|
|
769
|
+
Sentry.init({ beforeSend: dropThirdPartyOnlyError });
|
|
770
|
+
```
|
|
771
|
+
|
|
772
|
+
No Sentry package or configuration is bundled by FloPay. The predicate drops
|
|
773
|
+
only complete exception stacks with no app or `@flopay/*` frame and at least
|
|
774
|
+
one recognised browser-extension URL or Stripe `dahlia/stripe.js` path/module
|
|
775
|
+
marker. Anonymous frames may accompany that marker. Mixed, unrelated,
|
|
776
|
+
incomplete, and anonymous-only errors pass through unchanged. The `in_app`
|
|
777
|
+
flag is ignored because host rewriting may set it to `true` on third-party
|
|
778
|
+
frames.
|
|
779
|
+
|
|
762
780
|
Inline session creation classifies bounded failures without inspecting raw
|
|
763
781
|
errors: network/CORS/timeouts emit `transport_error`, 5xx responses emit
|
|
764
782
|
`server_error`, and malformed response discriminants emit `invalid_response`.
|
|
@@ -767,6 +785,16 @@ Stripe and PayPal SDK load/runtime failures emit `provider_runtime`. Inline
|
|
|
767
785
|
`validation_rejected` / `payment_declined` outcomes and never carry
|
|
768
786
|
`failureCategory`.
|
|
769
787
|
|
|
788
|
+
The same classification applies to React-owned saved-payment processing in
|
|
789
|
+
`auto` and `confirm` modes. An ordinary saved-payment `400` decline, a
|
|
790
|
+
structured-field `400`, or a `422` still falls back to the usable full checkout
|
|
791
|
+
and emits `operation.fallback`, but reports only the matching
|
|
792
|
+
`payment_declined` or `validation_rejected` outcome. Genuine server,
|
|
793
|
+
transport, malformed-response, and provider-runtime failures remain
|
|
794
|
+
categorized technical errors. This does not change fallback rendering or
|
|
795
|
+
merchant callback behavior, and no response body, provider payload, session
|
|
796
|
+
value, payment data, or raw error message is added to telemetry.
|
|
797
|
+
|
|
770
798
|
### SplitCardFormProps
|
|
771
799
|
|
|
772
800
|
Key payment-surface props include:
|