Normalize variant given to config

[LeBenLeBen]

Currently the variant prop is provided to the config class property as is, without any transformation. It means it can be an array or a string or whatever the user want it to be. I’m not sure this flexibility provides any added value. I personally like the simplicity of strings, but when you want to combine variants, it forces to end up with “complicated” tests to apply classes conditionally.

I usually use String.prototype.includes to test if a variant is present, but it’s fragile:

1. The variant might not exists, forcing to use a condition, the simplest being an optional chaining variant?.includes('something'), which I forget to add by default too often
2. This will match any occurrence of something, not only purple but also rebeccapurple for example. A behavior that is undesired most of the time if you split multiple variants with a space like I do

I feel like we should normalize this prop to always be a string and make it behave similarly to how the native class works: split by spaces and provide an API to access every property in a simple way. A Proxy could be great solution to return false by default and true when a variant is present; avoiding the necessity for conditional checks while keeping the syntax very short.