SKUSelector infinite loop fix

[tibiiordachevtex]

What problem is this solving?

There is an app called wishlist-io that uses the SKUSelector. When adding the prop "visibleVariations" to that SKUSelector, an infinite loop will occur breaking the functionality (the SKUSelector wont update, it will keep the default selection that is coming from the product-context).

One of the reason for the problem seems to be this useEffectSkipMount, that uses an object as a dependency. Even if the fields of the object stay the same, the reference change, so the useEffect will be executed, and the state of selectedVariation will change, causing a re-render.

This ramda deep compare that I added, just checks if the variation really changed.

How to test it?

In order to test, I created 1 workspace that illustrates the behaviour after the change.

workspace - tibidev; account - miniprix

Screenshots or example usage:

Here is a gif of how the selector acts before

It's not seen in the gif, but for a moment the selection changed, but then it is back to the default one from the product-context, this can be seen in the photo below.

Here is a gif of how the selector acts after

Describe alternatives you've considered, if any.

I tried to dive even deeper and see why the variation change reference in the first place, but I had no results after a while.

Related to / Depends on

How does this PR make you feel? 🔗

![https://media.giphy.com/media/l7fdqmHQ1jCg2HzQlx/giphy.gif](put .gif link here - can be found under "advanced" on giphy)

[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 😞

[vtex-io-docs-bot]

Beep boop 🤖

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

• There's nothing new to document 🤔
• I'll do it later 😞

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

• I just updated 🎉🎉