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
Context nodes should be able to be named, just as signals and computations.
Without names, context nodes don't have anything besides their value (which takes a second to inspect and identify) to identify different context nodes by.
Such change would need to be added to solid first—createContext doesn't have an option for that.
(PR adding that to solid: solidjs/solid#1266)
Then the debugger would have to be modified to send the name field to the extension.
Since the computations in solid have their name generated if one isn't passed using options, the generated names would have to also be displayed to the user. At least until that behavior is changed.
The text was updated successfully, but these errors were encountered:
Context nodes should be able to be named, just as signals and computations.
Without names, context nodes don't have anything besides their value (which takes a second to inspect and identify) to identify different context nodes by.
Such change would need to be added to solid first—createContext doesn't have an option for that.
(PR adding that to solid: solidjs/solid#1266)
Then the debugger would have to be modified to send the name field to the extension.
Since the computations in solid have their name generated if one isn't passed using options, the generated names would have to also be displayed to the user. At least until that behavior is changed.
The text was updated successfully, but these errors were encountered: