Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: add possibility to create actors without the implementation #697

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

Open
XavierGeerinck wants to merge 10 commits into dapr:main
base: main
Choose a base branch
Loading
from XavierGeerinck:master

Conversation

@XavierGeerinck
Copy link
Contributor

@XavierGeerinck XavierGeerinck commented May 1, 2025

Description

Long overdue, this PR solves the issue that when you are creating an Actor Proxy, that the implementation of the actor was required. There was a work around for it, but this PR makes it more concrete.

This PR also adds the possibility to use an interface class name that differs from the registered actor.

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #417

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Extended the documentation

Signed-off-by: Xavier Geerinck <xavier.geerinck@gmail.com>
Signed-off-by: Xavier Geerinck <xavier.geerinck@gmail.com>
Signed-off-by: Xavier Geerinck <xavier.geerinck@gmail.com>
Signed-off-by: Xavier Geerinck <xavier.geerinck@gmail.com>
Signed-off-by: Xavier Geerinck <xavier.geerinck@gmail.com>
Signed-off-by: Xavier Geerinck <xavier.geerinck@gmail.com>
Copy link
Contributor

At first glance, this appears to implement a breaking change as anyone currently using actors would have to rebuild their applications to support this. Is that intentional?

Signed-off-by: Xavier Geerinck <xavier.geerinck@gmail.com>
Copy link
Contributor Author

Added backwards-compatibility for the breaking change :)

WhitWaldo reacted with thumbs up emoji

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Actor client SDK requires actor implementation

AltStyle によって変換されたページ (->オリジナル) /