Changing parent UI affects children

[Arjeno]

We have this basic setup:

• Parent with UI
  • Child with UI
  • Child with UI

Each time the parent UI changes it will update the children UI as well, forcing an update. We want to keep the children pure, we do not need the parent UI settings.

I understand this can be handy in some cases, in some cases it may not be handy and will require a manual check in shouldComponentUpdate to see if the internal UI settings were updated. Is there any way to make this configurable? Just wondering what you guys think about this.

[tonyhb]

Good question. I think you're right that it could be configurable, and default to sharing state from parent -> child.

The idea of parent-level block scoping is useful when you build reusable components like pagination, which affects the parent set that loads data. The parent component might set the page UI state and the pagination component could modify it.

I'll add this to the 1.0 roadmap to make it an option.

Thanks @Arjeno

[Arjeno]

Thanks for the response @tonyhb. I didn't realize UI props were also settable from child to parent when they are shared like that. Thanks for considering making it an option!

[jshthornton]

I'd love this feature too.

Say I have a scene where I want a child component's ui to be different than another scene's child component's ui. You could pass down props, but then you have some information in props and some in state, which gets real messy real quick.

[tonyhb]

+1 thanks for the heads up @jshthornton. Work at Docker has been exceptionally busy pushing out a new version of our platform, getting back onto this now