Product Configurator Nested Lists

I see, thanks for that additional context! A couple more questions:

  • Would user selections ever change the specification name labels? Or is it just the options in each that change?
  • When you check the dependencies is it assumed that each selection is unique or does it need to be tied to the field it was selected from? In other words, are you checking against an object that looks more like ["Cat", "Persian", "4", "Cat Collar"] or {type: "Cat", breed: "Persian", legs: 4, accessories: "Cat Color"}?

This is my first time seeing this particular use case, but I can certainly see it being a common one. Coincidentally, another user recently asked a similar question here, but I think there may be a few different ways to approach this.