Closed alexweininger closed 1 year ago
Could we make the refresh implementation different on the node itself rather than having this weird edge case in the command defintion?
Like, if you call
GroupingTreeItem
's refresh, it's implementation will handle passing up the subscription/parent node? Or do we not have that capability anymore?
We haven't done it that way for v2, however that's probably a good approach.
Is it possible to do that now or should I just go ahead and approve this for merge, and we can leave an issue for it later?
Is it possible to do that now or should I just go ahead and approve this for merge, and we can leave an issue for it later?
I will change it sometime today (hopefully). 😄
Since this is sorta a special case, I think for now this implementation is fine. None of the solutions I have feel right since it's just for this one edge case.
Alright, definitely something to keep in mind when we convert a hefty boy like Functions.
Fixes #617