@motopays/pay-form 2.6.4-rc.8 → 2.6.4

package/CHANGELOG.md

@@ -1,13 +1,11 @@
 # Changelog
 
-## 2.6.4-rc.8
+## 2.6.4
 
 ### Added
 - Divider between payment methods now supports custom ordering of elements:
     previously divider was above apm-list always, now if apm-list is above requisites, divider is placed between apm-list and requisites and vice-versa.
-    And if apmsCollapse is enabled, requisites could be collapsed from now, if they placed after apm-list
-- New setting isPaymentMethodsCollapsible?:boolean added, which will later replace apmsCollapse?:boolean. More details in README.md
-
+    apmsCollapse flag remains unchanged, it will collapse only the APMs
 
 
 

package/README.md

@@ -257,8 +257,7 @@ export class AppComponent {
 | events                     | IEvents | The events configuration |
 | events.analytics           | { optional: boolean; required: boolean; } | The analytics events configuration. Optional is responsible for 'focus' events. Required is responsible for 'click' events. Read more about analytics events in the Analytics section |
 | events.error               | boolean | The error events configuration. If true, the error events will be emitted; otherwise, they will not  |
-| apmsCollapse               | boolean | __Will be replaced with *isPaymentMethodsCollapsible*__. The apms collapse configuration. If true, the 'or use alternative methods' text will be clickable and will control whether the apms are shown or not. By default, if true, the apms will be collapsed.   |
-| isPaymentMethodsCollapsible               | boolean | The payment method collapse configuration. If true, the 'or use alternative methods' text will be clickable and will control whether the payment methods below the divider are shown or not. By default, if true, the payment methods below the divider will be collapsed.|
+| apmsCollapse               | boolean | The apms collapse configuration. If true, the 'or use alternative methods' text will be clickable and will control whether the apms are shown or not. By default, if true, the apms will be collapsed.   |
 | paymentFlow                | IPaymentFlowSettings | The payment flow configuration |
 | paymentFlow.tokenizeCard   | boolean | If true, than for not 'default' paymentFlow.type card requisites will be tokenized (only for 'invoice-overridden' and 'payment-overridden' paymentFlow.type) |
 | paymentFlow.type           | TPaymentFlow | If 'invoice-overridden' and createInvoice callback provided to the payment form, the createInvoice callback will be called with the invoice generated by the payment form. After receiving the invoice from the createInvoice callback, the payment process will proceed according to the default scenario. If 'payment-overridden' and makePayment callback provided to the payment form, the entire payment process will be handled through the makePayment callback with the invoice generated by the payment form |

package/index.d.ts

@@ -151,7 +151,6 @@ export interface ISettings {
 	requiredFieldsBehavior?: IRequiredFieldsBehavior;
 	events?: IEvents;
 	apmsCollapse?: boolean;
-	isPaymentMethodsCollapsible?: boolean;
 	paymentFlow?: IPaymentFlowSettings;
 	googlePay?: IGooglePayIntegratorSettings;
 }