Feat added unavailable class name

vtex-apps / store-components

Default VTEX store components

51 stars 142 forks source link

Feat added unavailable class name #1101

Closed jorgeAcostaVTEX closed 9 months ago

jorgeAcostaVTEX commented 9 months ago

What problem is this solving?

PDP Sku selector shows unavailable items crossed out. Some clients require to hide these items via CSS with a CSS HANDLE

How to test it?

Go to the workspace and use css to hide class unavailable

Workspace

Screenshots or example usage:

Describe alternatives you've considered, if any.

Related to / Depends on

How does this PR make you feel? :link:

![](put .gif link here - can be found under "advanced" on giphy)

vtex-io-ci-cd[bot] commented 9 months ago

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)
[x] 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 😞

vtex-io-docs-bot[bot] commented 9 months ago

Beep boop :robot:

I noticed you didn't make any changes at the docs/ folder

[x] There's nothing new to document :thinking:
[ ] I'll do it later :disappointed:

In order to keep track, I'll create an issue if you decide now is not a good time

[ ] I just updated :tada::tada:

vtex-io-ci-cd[bot] commented 9 months ago

Your PR has been merged! App is being published. :rocket: Version 3.171.0 → 3.172.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.172.0

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. :book: