Typo in Akka Typed Persistence Docs (#26635)
This commit is contained in:
parent
5a47df4681
commit
95fce88b2d
1 changed files with 2 additions and 2 deletions
|
|
@ -204,7 +204,7 @@ Java
|
||||||
given to the `forStateType` of the `CommandHandlerBuilder` and the match cases in the builders.]
|
given to the `forStateType` of the `CommandHandlerBuilder` and the match cases in the builders.]
|
||||||
@scala[The command handler to process each command is decided by first looking at the state and then the command.
|
@scala[The command handler to process each command is decided by first looking at the state and then the command.
|
||||||
It typically becomes two levels of pattern matching, first on the state and then on the command.]
|
It typically becomes two levels of pattern matching, first on the state and then on the command.]
|
||||||
Delegating to methods is a good practise because the one-line cases give a nice overview of the message dispatch.
|
Delegating to methods is a good practice because the one-line cases give a nice overview of the message dispatch.
|
||||||
|
|
||||||
Scala
|
Scala
|
||||||
: @@snip [BlogPostExample.scala](/akka-persistence-typed/src/test/scala/docs/akka/persistence/typed/BlogPostExample.scala) { #command-handler }
|
: @@snip [BlogPostExample.scala](/akka-persistence-typed/src/test/scala/docs/akka/persistence/typed/BlogPostExample.scala) { #command-handler }
|
||||||
|
|
@ -503,4 +503,4 @@ Message deletion does not affect the highest sequence number of the journal, eve
|
||||||
It is up to the journal implementation whether events are actually removed from storage.
|
It is up to the journal implementation whether events are actually removed from storage.
|
||||||
Deleting events prevents future replaying of old events to apply new state.
|
Deleting events prevents future replaying of old events to apply new state.
|
||||||
|
|
||||||
@@@ note
|
@@@ note
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue