Shipping methods not refreshed after country change in checkout

[tniezg]

Current behavior

Shipping methods don't update in checkout whenever the shipping country is changed.

Expected behavior

Update shipping informaiton and download current shipping methods when the country is changed.

Steps to reproduce the issue

• Add products to cart
• Go to checkout
• Go to Shipping step
• Change country

Result: Shipping methods under the Shipping form stay the same. @change prop isn't used to call changeCountry inside Shipping.ts.

Repository

Occurs in stock VS, default theme.

Can you handle fixing this bug by yourself?

• YES
• NO

Which Release Cycle state this refers to? Info for developer.

Pick one option.

• This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
• This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
• This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

• Browser: Google Chrome Version 73.0.3683.86 (Official Build) (64-bit)
• OS: macOS 10.14.3
• Node: 8.15.0
• Code Version: Up to this commit 215aa17

Additional information

Proposed fix: Based on https://vuejs.org/v2/guide/components-custom-events.html add a model key inside BaseSelect which remaps v-bind to emit change event instead of the default event (input) and $emit change instead of input.

Where to make the change: https://github.com/DivanteLtd/vue-storefront/blob/master/src/themes/default/components/core/blocks/Form/BaseSelect.vue#L33

[revlis-x]

Using @change.native works.

[pkarw]

@revlis-x - thanks for You insight! Could You please prepare a Pull Request with a fix