Its adding "WeightUnit" (mg, µg) to "LengthUnit" . May need to fix.
Yes, the value of "needs-data" is the "key" in token replace data, not actually an "entity_type_id".
In the default multi-step checkout flow, the offsite payment record is handled in "Payment Process" step. commerce_payment record should be created in the "forms" defined in the related OffsitePaymentGateway.
However, in this module, "Stripe Payment Element" payment info is handled in "Stripe Review" checkout pane. The related record should be created once with the `payment_intent` id and order info, before user interaction, so the webhook processor can handle related payment properly.
In my opinion,
1. the form Drupal\commerce_stripe\PluginForm\OffsiteRedirect\PaymentOffsiteForm should be rewritten to display the "Stripe Payment Element".
2. "Stripe Review" checkout pane is not required when using "Stripe Payment Element" gateway.
3. The "stored" payment_method may handled asyncly in webhook processor, but not in `StripePaymentElement::onReturn` as not all payment type in stripe support this feature.
kongkx → made their first commit to this issue’s fork.
`config/schema/user_redirect.schema.yml` is needed to serialize the config value properly.
I think add context to all unit string is better.
self::MILLIMETER => t('mm', [], ['context' => 'length unit']),
self::CENTIMETER => t('cm', [], ['context' => 'length unit']),
self::METER => t('m', [], ['context' => 'length unit']),
self::KILOMETER => t('km', [], ['context' => 'length unit']),
self::INCH => t('in', [], ['context' => 'length unit']),
self::FOOT => t('ft', [], ['context' => 'length unit']),
self::NAUTICAL_MILE => t('M', [], ['context' => 'length unit']),
The pin widgets are binded with "view_mode". It's required to enable pin on "Field Display" of different "view_mode" of Entity/Bundle and then add pins for the specific view_mode on the edit form.