Merge pull request #752 from UnAfraid/patch-1
Fixed typo in State-Machines wiki page
This commit is contained in:
commit
05db723802
@ -70,8 +70,7 @@ Now, after your naughty bot retaliates, the user can say "go left or else" to fo
|
|||||||
|
|
||||||
## Complete Example
|
## Complete Example
|
||||||
```java
|
```java
|
||||||
public static class ReplyFlowBot extends AbilityBot {
|
public class ReplyFlowBot extends AbilityBot {
|
||||||
public class ReplyFlowBot extends AbilityBot {
|
|
||||||
public ReplyFlowBot(String botToken, String botUsername) {
|
public ReplyFlowBot(String botToken, String botUsername) {
|
||||||
super(botToken, botUsername);
|
super(botToken, botUsername);
|
||||||
}
|
}
|
||||||
@ -105,7 +104,7 @@ public static class ReplyFlowBot extends AbilityBot {
|
|||||||
private Predicate<Update> hasMessageWith(String msg) {
|
private Predicate<Update> hasMessageWith(String msg) {
|
||||||
return upd -> upd.getMessage().getText().equalsIgnoreCase(msg);
|
return upd -> upd.getMessage().getText().equalsIgnoreCase(msg);
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
## Inline Declaration
|
## Inline Declaration
|
||||||
As you can see in the above example, we used a bottom-up approach. We declared the leaf replies before we got to the root reply flow.
|
As you can see in the above example, we used a bottom-up approach. We declared the leaf replies before we got to the root reply flow.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user