Skip to content
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

fix: allow messages with the same name from different packages #1643

Merged
merged 1 commit into from
Aug 2, 2022

Conversation

jroper
Copy link
Contributor

@jroper jroper commented Aug 2, 2022

Fixes #1625

This allows messages with the same name but different packages to be used by the same service by prefixing the messages generated serializer names with the underscore separated package name if they came from if they come frome a different package to the package the service is declared in.

Fixes akka#1625

This allows messages with the same name but different packages to be
used by the same service by prefixing the messages generated serializer
names with the underscore separated package name if they came from if
they come frome a different package to the package the service is
declared in.
Copy link
Member

@raboof raboof left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neat!

@raboof raboof merged commit 9c613f4 into akka:main Aug 2, 2022
@jroper jroper deleted the duplicate-message-names branch August 3, 2022 01:53
@jroper
Copy link
Contributor Author

jroper commented Aug 3, 2022

Could I get an akka-grpc release with this? I'm somewhat blocked on a customer issue until I can get this fix (I can work around it, but that will involve making breaking changes to a public API later when we want to move to the fix).

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

Successfully merging this pull request may close these issues.

Bad naming for message classes of the same name but from different packages yielding collisions
2 participants