1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
use crate::event::Event;
pub mod stream;
pub fn channel(event: Event) -> Option<crate::channel::Event> {
match event {
Event::Channel(channel) => Some(channel),
_ => None,
}
}
pub fn message(event: Event) -> Option<crate::message::Event> {
match event {
Event::Message(event) => Some(event),
_ => None,
}
}
pub fn user(event: Event) -> Option<crate::user::Event> {
match event {
Event::User(event) => Some(event),
_ => None,
}
}
pub mod channel {
use crate::channel::{Event, event};
pub fn created(event: Event) -> Option<event::Created> {
match event {
Event::Created(event) => Some(event),
Event::Deleted(_) => None,
}
}
pub fn deleted(event: Event) -> Option<event::Deleted> {
match event {
Event::Deleted(event) => Some(event),
Event::Created(_) => None,
}
}
}
pub mod message {
use crate::message::{Event, event};
pub fn sent(event: Event) -> Option<event::Sent> {
match event {
Event::Sent(event) => Some(event),
Event::Deleted(_) => None,
}
}
pub fn deleted(event: Event) -> Option<event::Deleted> {
match event {
Event::Deleted(event) => Some(event),
Event::Sent(_) => None,
}
}
}
pub mod user {
use crate::user::{Event, event};
// This could be defined as `-> event::Created`. However, I want the interface to be consistent
// with the event stream transformers for other types, and we'd have to refactor the return type
// to `-> Option<event::Created>` the instant users sprout a second event, anyways.
#[allow(clippy::unnecessary_wraps)]
pub fn created(event: Event) -> Option<event::Created> {
match event {
Event::Created(event) => Some(event),
}
}
}
|
