-
Notifications
You must be signed in to change notification settings - Fork 34
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
@boopickleWireProtocol macro expansion error due to empty parameter list in event sourced entity api #68
Comments
@SemanticBeeng Hi. |
Ok, DM exchanged showed that the problem is with methods shaped the following way (with an empty param list:
Quick workaround is to remove the parens. I'll try to tune the macro to handle this case properly. @SemanticBeeng Could you please alter the ticket title (I can't)? |
Vladimir advised the macro crash is due to the empty parameter list in
Will keep it open to fix this rough edge of the macro. |
Actually I’d rather forbid empty params list methods at all :) They are used to mark something impure, which should not be a case. |
I would be perfectly okay to close, ofc. |
It's more about code-style that communicates purity. Aecor calls itself |
A nice error message would be great. |
@notxcain I am getting this as soon as I add a method in my event sourced entity api returning
*Status
. The*Status
is implemented similar toBookingStatus
from @vpavkin 's tutorial.The only thing I can see different is that my
*Status
is in a different sbt module than the entity.But also tried moving it to same sbt module and getting same
Any idea of what might cause this?
Not likely this to be an
aecor
bug but maybe others will run into it so worth having it here.The text was updated successfully, but these errors were encountered: