-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actor client SDK requires actor implementation #417
Labels
Comments
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
XavierGeerinck
modified the milestones:
Dapr Node.js SDK - v3.1.0,
Dapr Node.js SDK - v3.2.0
Apr 25, 2023
shubham1172
modified the milestones:
Dapr Node.js SDK - v3.2.0,
Dapr Node.js SDK - v3.3.0
Jun 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems the to use the JS SDK for actors, the client invoking a remote actor needs a copy of the implementation code in order to register the actor... drilling into the code, it looks like the only reason for this is to get the name of the actor type. Would it be possible to have an overload to create the proxy builder that does not require passing in the implementation, but rather just the actor type name?
The text was updated successfully, but these errors were encountered: