Right now the variation label is the sku. The sku is not meant to be user friendly, it's a machine name.
A variation is always identified by its attributes. So we should construct a label from that. "Small, Blue"
If there are no attributes, that means there's always only one variation. We can call it "Default".

We have this data on the entity already, so we don't need to store it in a property, we can create it on the fly.
This helps us avoid the problem of the label getting out of date if the attribute gets renamed or gets a new translation.

Comments

bojanz created an issue. See original summary.

  • bojanz committed 577421a on 8.x-2.x
    Issue #2606252 by bojanz: Rework the variation label
    
bojanz’s picture

Status: Active » Fixed

Done.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.