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
as of v0.6.2 the second time you call detach on a binding it throws an error since the binding doesn't have the _signal and _listener properties anymore. I think the proper behavior would be to simply return null instead of throwing an error.. (detach() usually returns the listener)
I think it doesn't make any sense for a binding exist without a listener/signal but throwing errors like this ain't fun or necessary.. (specially if calling detach multiple times..)
maybe add a new method like isBound() that checks if Binding still references a Signal..
The text was updated successfully, but these errors were encountered:
as of v0.6.2 the second time you call
detach
on a binding it throws an error since the binding doesn't have the_signal
and_listener
properties anymore. I think the proper behavior would be to simply returnnull
instead of throwing an error.. (detach()
usually returns thelistener
)I think it doesn't make any sense for a binding exist without a listener/signal but throwing errors like this ain't fun or necessary.. (specially if calling
detach
multiple times..)maybe add a new method like
isBound()
that checks if Binding still references a Signal..The text was updated successfully, but these errors were encountered: