You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I often see things like context state.update(...) on the support channels. Could be nice to detect some common cases where context isn't necessary, even if it appears to be, initially. (Of course, detecting every case would be very inefficient, maybe even generally impossible. But maybe we can at least tell if we're just constructing a built-in element known to not need context without any particular logic.)
Could be nice to add a hint depending on what one attempted to do.
However, we should make sure to not warn if the user has some logic that would lead to a valid usage of context, e.g. check a variable and return state.update() if true, state.get() if false. So, we should not be too annoying.
Use Case
Help users better understand context's use cases.
The text was updated successfully, but these errors were encountered:
Description
I often see things like
context state.update(...)
on the support channels. Could be nice to detect some common cases where context isn't necessary, even if it appears to be, initially. (Of course, detecting every case would be very inefficient, maybe even generally impossible. But maybe we can at least tell if we're just constructing a built-in element known to not need context without any particular logic.)Could be nice to add a hint depending on what one attempted to do.
However, we should make sure to not warn if the user has some logic that would lead to a valid usage of context, e.g. check a variable and return state.update() if true, state.get() if false. So, we should not be too annoying.
Use Case
Help users better understand context's use cases.
The text was updated successfully, but these errors were encountered: