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
The way actor types are implemented now means that no type checking is being performed on the types of messages that the actors from a spawn function actually processes. In cases where the spawn function directly calls the spawn function from @nact/core, the message type is explicitly mentioned in the signature of the main actor function, but in more advanced actor types – like those derived from DerivedAuthority – this is not the case.
The text was updated successfully, but these errors were encountered:
The way actor types are implemented now means that no type checking is being performed on the types of messages that the actors from a spawn function actually processes. In cases where the spawn function directly calls the spawn function from @nact/core, the message type is explicitly mentioned in the signature of the main actor function, but in more advanced actor types – like those derived from DerivedAuthority – this is not the case.
The text was updated successfully, but these errors were encountered: