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
Is it intentional that the implementations of the ActorCallError, QueryCallRejectedError, and UpdateCallRejectedError classes do not use Object.setPrototypeOf?
The issue is that it currently prevents a type-safe check for an error thrown using this code:
Hey!
Is it intentional that the implementations of the
ActorCallError
,QueryCallRejectedError
, andUpdateCallRejectedError
classes do not useObject.setPrototypeOf
?The issue is that it currently prevents a type-safe check for an error thrown using this code:
The only type-safe check that works now is
e instanceof AgentError
, which is useless because AgentError has no properties to check.The text was updated successfully, but these errors were encountered: