We want to backport the recent SolidusStarterFrontend changes to v3.3 branch so that the planned SolidusBraintree 2.0.0 would be compatible with Solidus and SolidusStarterFrontend v3.3.
Background
We discovered in https://github.com/solidusio/solidus_braintree/issues/104 that the planned SolidusBraintree 2.0.0 gem is currently not compatible with Solidus 3.3, and thus would require Solidus 3.4 (or Solidus 3.4.0.dev) to work.
By backporting the recent SolidusStarterFrontend changes to v3.3 branch, SolidusBraintree 2.0.0 would hopefully be compatible with Solidus and SolidusStarterFrontend v3.3, and thus we won't have to wait for Solidus 3.4 to be released before releasing SolidusBraintree 2.0.0.
Goal
We want to backport the recent SolidusStarterFrontend changes to v3.3 branch so that the planned SolidusBraintree 2.0.0 would be compatible with Solidus and SolidusStarterFrontend v3.3.
Background
We discovered in https://github.com/solidusio/solidus_braintree/issues/104 that the planned SolidusBraintree 2.0.0 gem is currently not compatible with Solidus 3.3, and thus would require Solidus 3.4 (or Solidus 3.4.0.dev) to work.
By backporting the recent SolidusStarterFrontend changes to v3.3 branch, SolidusBraintree 2.0.0 would hopefully be compatible with Solidus and SolidusStarterFrontend v3.3, and thus we won't have to wait for Solidus 3.4 to be released before releasing SolidusBraintree 2.0.0.
Tasks