You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
let's write up a list of parity-changes required to move the iOS and Android version together:
Rename initPayment to initialize
Remove the ability to store keys in the tiapp.xml (security reasons, the keys are not encrypted I think) - No blocker
Require the configuration key to be an instance of the Configuration proxy (no object, to keep it more structured and be able to hook into possible events that will be exposed in the future)
Require the items key to be an array of the PaymentItem proxy instances (see above reasons). I noticed there is no PaymentItem proxy so far, so if possible, create that one for parity
Ensure all events from iOS also exist on Android or list the ones that are not covered. Some examples of important events: paymentDidCancel , paymentWillComplete and paymentDidComplete (For example, I don't see paymentWillComplete in the Android docs so far)
Thank you so much for the efforts! It will be amazing to have a centralized and up-to-date PayPal module for the developers again!
The text was updated successfully, but these errors were encountered:
Hey @AppWerft <https://github.com/appwerft>,
let's write up a list of parity-changes required to move the iOS and
Android version together:
* Rename |initPayment| to |initialize|
* Remove the ability to store keys in the tiapp.xml (security
reasons, the keys are not encrypted I think) - No blocker
* Require the |configuration| key to be an instance of the
|Configuration| proxy (no object, to keep it more structured and
be able to hook into possible events that will be exposed in the
future)
* Require the |items| key to be an array of the |PaymentItem| proxy
instances (see above reasons). I noticed there is no |PaymentItem|
proxy so far, so if possible, create that one for parity
* Ensure all events from iOS also exist on Android or list the ones
that are not covered. Some examples of important events:
|paymentDidCancel|, |paymentWillComplete| and |paymentDidComplete|
(For example, I don't see |paymentWillComplete| in the Android
docs so far)
Thank you *so much* for the efforts! It will be amazing to have a
centralized and up-to-date PayPal module for the developers again!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC24DZNZLQnc-6XWScVlg_FQvl5KR_7Vks5r8_06gaJpZM4Nk3Jg>.
Hey @AppWerft,
let's write up a list of parity-changes required to move the iOS and Android version together:
initPayment
toinitialize
configuration
key to be an instance of theConfiguration
proxy (no object, to keep it more structured and be able to hook into possible events that will be exposed in the future)items
key to be an array of thePaymentItem
proxy instances (see above reasons). I noticed there is noPaymentItem
proxy so far, so if possible, create that one for paritypaymentDidCancel
,paymentWillComplete
andpaymentDidComplete
(For example, I don't seepaymentWillComplete
in the Android docs so far)Thank you so much for the efforts! It will be amazing to have a centralized and up-to-date PayPal module for the developers again!
The text was updated successfully, but these errors were encountered: