[RFC] Decouple variables passed to child components from parent component's logic about fluent-ui-react

[levithomason]

After thinking this through more, I also think proposal 1 is ideal. It introduces no new concepts or patterns. It is both more simple than proposal 2 and more powerful.

[miroslavstastny]

My (still the same) opinion is if we access theme variables in component source, layers are broken.
I completely agree with the proposal to decouple it, I love Proposal 1.

[kuzhelov]

Agree with all the points provided. We've had similar discussion with @miroslavstastny where exactly the same points were raised by him - at that point we've decided to pass variables directly in component's logic, primarily for the sake of not introducing additional complexity for theme mechanisms that were just introduced then (and, thus, were not exploited enough to be considered as robust solution).

Speaking of the options suggested - I would definitely support the first one, as it suggests clear path that doesn't change but extends the approach we are using now - and, thus, it is not associated with significant increase of complexity. Also, this one seems to be flexible enough, so that with this one we would be able to address quite broad set of scenarios.

Not saying 'no' to the second option, though - but would rather wait once this concept will solidify in our minds, for the sake of us being absolutely sure about what we are buying for additional efforts laid in this direction, as well as whether this concept is able to cover all the cases we are interested in (and how flexible it would be to cover potentially emerged edge-cases)

[kuzhelov]

thanks - let me introduce PR for having more concrete discussion over the first option then..