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
Currently we only log error in the noble-winrt package as noble has a rather bad error handling story (noble/noble#830). The problem is that it only emits a warning if e.g. a peripheral is not found and there is no way for bindings to return an error.
A proper solution would be to add a error argument in the bindings interface and the noble interface to let bindings error bubble up to the user.
Currently we only log error in the noble-winrt package as noble has a rather bad error handling story (noble/noble#830). The problem is that it only emits a warning if e.g. a peripheral is not found and there is no way for bindings to return an error.
A proper solution would be to add a
error
argument in the bindings interface and the noble interface to let bindings error bubble up to the user.The text was updated successfully, but these errors were encountered: