-
Notifications
You must be signed in to change notification settings - Fork 0
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
Give code examples in Messaging concepts #14
Comments
Use step 3 from https://spine.io/ index page. |
meizabel
referenced
this issue
in meizabel/SpineEventEngine.github.io
Apr 8, 2019
- Renaming getBuilder() into builder(), - Adding a note to Command Handler and Event Subscriber concepts.
meizabel
referenced
this issue
in meizabel/SpineEventEngine.github.io
Apr 8, 2019
- Adding note contents to Command Handler and Event Subscriber concepts.
meizabel
referenced
this issue
in meizabel/SpineEventEngine.github.io
Apr 11, 2019
Fixing code example in Event Subscriber concept. Removing extra method from code sample.
alexander-yevsyukov
referenced
this issue
in SpineEventEngine/SpineEventEngine.github.io
Apr 12, 2019
Adding code example in Event Subscriber concept; renaming getBuilder() into builder to address issue #138
@alexander-yevsyukov you have already modified the |
alexander-yevsyukov
transferred this issue from SpineEventEngine/SpineEventEngine.github.io
Jan 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to name annotations and method conventions for the message handlers such as “Command Handler” or “Event Subscriber”.
There should be also a small code snippet which displays how a method which handles this kind of messages looks like.
The text was updated successfully, but these errors were encountered: