Payments made in Background

Offen
  • Stimmt etwas nicht?
#12 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Dokumentation
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
typescript
Bereich
documentation, mobile, payments

Rechercherichtung

Start by reviewing the plugin's purchase observable and the PaymentEvent.Context values, especially FINALIZING_ORDER and CONNECTING_STORE, in the context of app-start events and store-triggered purchases. Done means documenting the supported background-purchase behavior, explaining those context values, and addressing the questions about test coverage and project status.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

First of all: awesome job to have an official payment library, much needed, thank you for that!

First question: does the plugin supports purchases made in background? E.g. it is possible to redeem offer codes in the respective stores what triggers a purchase event as soon as the app starts. Is it sufficient to connect to the observable right after app start to retrieve those events triggered in background opposed to those triggered in the app by a user?

Second: Also I would highly appreciate some documentation on the purpose of the different values of PaymentEvent.Context (especially FINALIZING_ORDER and CONNECTING_STORE).

Third: How would you rate the state of development of the plugin regarding test coverage and open (internal) issues? We currently use the ProPlugin purchase plugin and consider switching to this one since it is more up to date and we have ongoing issues with the ProPlugin implementation.

Thank you so much for the effort put into this!

Vorherrschende Sprache
TypeScript
Sterne
35
Forks
13
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus NativeScript/payments

Alle Issues in NativeScript/payments

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.