Do we still need to use constraints in the dapp code?
edchat opened this issue · comments
Since the default constraints was done with #35 and most apps don't need to set constraints, does dapp still need to support constraints in the config, and does the dapp code need to keep track of the constraint for a view, or can it be determined whenever it is needed.
I think the constraints are very helpful in dealing with knowing if a childView should replace another childView or should be shown along with another childView. It gives the app developer a way to control this in case they want something different than we expect. Part of the way we are able to find a good default for delite is that we know that containers with a selectedChildId replace their children, but if we don't have a way to check that for other frameworks, then we will be back to requiring the constraints to be set in the config.