Update: SKU Selector logic for default

[beatrizmaselli]

What problem is this solving?
The SKU selector, when there were multiple SKUs with the same specifications, was always selecting the first SKU without considering the product’s sale feasibility. This issue could lead to displaying an SKU that is not actually available for purchase, affecting customer experience and conversions.

How to test it?
Ensure that you have multiple SKUs with identical specifications but differing in sale feasibility. Verify that the SKU selector now prioritizes SKUs that are available for sale when displaying the SKU options in the context.

Workspace

Screenshots or example usage:

Before adjustment:

After adjustment:

Describe alternatives you've considered, if any.
No significant alternatives were considered, as the focus was on improving SKU selection based on sale feasibility.

How does this PR make you feel? 🔗

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the dependency URLs in the devDependencies section of the react/package.json file. This ensures that the dependencies are downloaded over a secure communication channel, mitigating the risk of MITM attacks.

• Locate the devDependencies section in the react/package.json file.
• Replace the HTTP URLs with HTTPS URLs for all dependencies listed under devDependencies.
• Ensure that the functionality remains unchanged by verifying that the new HTTPS URLs are correct and accessible.

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the dependency URLs in the devDependencies section of the react/package.json file. This ensures that the dependencies are downloaded over a secure communication channel, mitigating the risk of MITM attacks.

• Locate the devDependencies section in the react/package.json file.
• Replace all instances of http:// with https:// in the URLs of the dependencies.
• Ensure that the URLs are accessible over HTTPS and that the functionality remains unchanged.

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the URLs used to download dependencies in the react/package.json file. This ensures that the dependencies are downloaded over a secure communication channel, protecting against MITM attacks.

• Locate the URLs in the devDependencies section that use the HTTP protocol.
• Change the protocol from http to https for each of these URLs.
• Ensure that the new URLs are correct and accessible over HTTPS.

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the dependency URLs in the package.json file. This ensures that the dependencies are downloaded over a secure, encrypted communication channel, mitigating the risk of MITM attacks.

• General Fix: Replace all instances of http:// with https:// in the dependency URLs.
• Detailed Fix: Specifically, update lines 57 to 75 in the react/package.json file to use HTTPS instead of HTTP.
• Required Changes: No additional methods, imports, or definitions are needed. The change is limited to modifying the URLs.

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the dependency URLs in the package.json file. This ensures that the dependencies are downloaded over a secure, encrypted communication channel, mitigating the risk of MITM attacks.

• Open the react/package.json file.
• Locate the lines where dependencies are specified with HTTP URLs.
• Change the protocol from http to https for each of these URLs.

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the URLs used to download dependencies in the devDependencies section of the package.json file. This ensures that the dependencies are downloaded over a secure communication channel, mitigating the risk of MITM attacks.

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the dependencies listed in the devDependencies section of the package.json file. This ensures that the dependencies are downloaded over a secure communication channel, mitigating the risk of MITM attacks.

• Locate the devDependencies section in the react/package.json file.
• Replace all instances of http:// with https:// in the URLs for the dependencies.

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the URLs used to download dependencies in the package.json file. This ensures that the dependencies are downloaded over a secure communication channel, mitigating the risk of MITM attacks.

• General Fix: Update all dependency URLs in the package.json file to use HTTPS instead of HTTP.
• Detailed Fix: Specifically, change the protocol for the URLs listed under devDependencies from HTTP to HTTPS.
• Files/Regions/Lines to Change: The changes will be made in the react/package.json file, specifically lines 65 to 75.
• Requirements: No additional methods, imports, or definitions are needed to implement these changes.

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the dependency URLs in the devDependencies section of the react/package.json file. This ensures that the dependencies are downloaded over a secure, encrypted communication channel, mitigating the risk of MITM attacks.

To fix the problem, we need to change the protocol from HTTP to HTTPS for all the URLs used to download dependencies in the react/package.json file. This ensures that the dependencies are downloaded over a secure communication channel, protecting against MITM attacks.

• Locate the URLs in the devDependencies section that use the HTTP protocol.
• Change the protocol from http to https for each of these URLs.
• Ensure that the new URLs are correct and accessible over HTTPS.

[beatrizmaselli]

LGTM

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 3.175.1 → 3.176.0

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.store-components@3.176.0

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖