Dependency on BuildContext

[Solido]

Just an open discussion on how and why we depend of context to connect Signal.

T watch(BuildContext context) => watchSignal<T>(context, this);

This is very representative. I would rather have our own object, like riverpod is doing
with scope or SolidJs with SolidContext.

The most important advantage can be to have full independence from Flutter.

[Kypsis]

I think the usual argument against rolling your own from the community is that it makes it harder to remove the package in the future (for whatever reason). But saying that there is this bit in Riverpod docs: https://riverpod.dev/docs/essentials/faq#why-do-we-need-to-extend-consumerwidget-instead-of-using-the-raw-statelesswidget

[rodydavis]

The actual dependency is on Element which BuildContext extends but made it BuildContext for the convenience of using inside of a statefull widget (since it may not be mounted)