This is the official Magento 2 extension for the logistics company PostNL. Add shipping options and parcelshops to your checkout. Create labels with track and trace functionality from the backend.
58
stars
61
forks
source link
[QUESTION] Ship-to summary does not change when the housenumber is edited: how to fix #367
Question
When a customer enters its address using the address check, the address gets correctly set in the sidebar shipping information (ship-to). However when the address is already filled, changing only the housenumber does not change the ship-to information in the sidebar.
The sidebar (module-checkout/view/frontend/web/js/view/shipping-information/list.js ) is subscribed to the quote.shippingAddress. When I load that UI module in my browser using:
require('uiRegistry').get('checkout.sidebar.shipping-information.ship-to');
I see that the customAttributes (tig_housenumber in this case) are not updated when only the housenumber is changed. Thus, changing only the housenumer does not change the quote.shippingAddress which does not trigger a reload of the ship-to information.
fyi: the address does get changed in the checkoutProvider
So I guess I see what the problem is, I am however a bit unsure about the correct solution. Is there any way we can observe a change in the tig_housenumber and still receive the correct address to trigger the createRendererComponent function in the list.js (which I guess we would need to make with a mixin?). Or is there a smarter way to do this?
Stack Magento: 2.4.4 Module PostNL: 1.12.5
Question When a customer enters its address using the address check, the address gets correctly set in the sidebar shipping information (ship-to). However when the address is already filled, changing only the housenumber does not change the ship-to information in the sidebar.
The sidebar (module-checkout/view/frontend/web/js/view/shipping-information/list.js ) is subscribed to the quote.shippingAddress. When I load that UI module in my browser using: require('uiRegistry').get('checkout.sidebar.shipping-information.ship-to'); I see that the customAttributes (tig_housenumber in this case) are not updated when only the housenumber is changed. Thus, changing only the housenumer does not change the quote.shippingAddress which does not trigger a reload of the ship-to information. fyi: the address does get changed in the checkoutProvider
So I guess I see what the problem is, I am however a bit unsure about the correct solution. Is there any way we can observe a change in the tig_housenumber and still receive the correct address to trigger the createRendererComponent function in the list.js (which I guess we would need to make with a mixin?). Or is there a smarter way to do this?
Any help would be appreciated