Daniel P H Fox

Been drafting out some approaches over in the Discord with some others - arriving at this rough first draft of a concrete implementation of call-stack-based cascades that doesn't interfere with...

Some further clarification on my issue. Suppose we create a themeable Button component using a theme cascade: ```Lua local themes = { dark = { buttonBG = Color3.new(0.5, 0.75, 1),...

Here's a second draft implementation of Cascades, which cascades values down the instance hierarchy rather than the call stack. This one uses special keys for the send/receive interface: ```Lua local...

Here's a third draft implementation of Cascades, again instance-based rather than call-stack based, but this time exposing a more flexible API that doesn't use special keys: ```Lua local function Cascade(defaultValue:...

Interesting thought which I don't have time to flesh out right now. Suppose you have a cascading 'text colour' which you apply to some text labels, which you can change...

> I personally would not be a fan of lazy loading and loose coupling in the context of this library. Especially in Roblox, it tends to give a far worse...

Deferring to v0.3

I think the issue here is fundamental to how Roblox is designed - the nil parent does not have a single responsibility. You cannot tell whether an instance in nil...

I'm currently leaning towards the latter, by the way; it's the prevailing wind with Roblox development nowadays, and would lead to a simpler system. The decision would then become 'which...

But hey! On the bright side, that gives us a nice declarative way to destroy instances - use a Computed for Parent and return nil to destroy 😛 (though maybe...