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
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
//! `ndjson-stream` offers a variety of NDJSON-parsers which accept data in chunks and process these
//! chunks before reading further, thus enabling a streaming-style use. The crate offers a low-level
//! interface in the [engine] module and more high-level interfaces for synchronous and asynchronous
//! NDJSON processing, which are available at the crate root (see for example [from_iter]). The
//! parser accepts any input which implements the [AsBytes](as_bytes::AsBytes) trait, which are the
//! most common data containers in core Rust and the standard library (e.g. `Vec<u8>` or `&str`).
//!
//! `ndjson-stream` uses the [serde_json] crate to parse individual lines. Hence, the output type of
//! the parser must implement [Deserialize](serde::Deserialize).
//!
//! # High-level example
//!
//! As an example, we will look at the iterator interface. The most basic form can be instantiated
//! with [from_iter]. We have to provide an iterator over data blocks, implementing
//! [AsBytes](as_bytes::AsBytes), and obtain an iterator over parsed NDJSON-records. Actually, the
//! exact return type is a `Result` which may contain a JSON-error in case a line is not valid JSON
//! or does not match the schema of the output type.
//!
//! The example below demonstrates both the happy-path and parsing errors.
//!
//! ```
//! use serde::Deserialize;
//!
//! #[derive(Debug, Deserialize, Eq, PartialEq)]
//! struct Person {
//! name: String,
//! age: u16
//! }
//!
//! let data_blocks = vec![
//! "{\"name\":\"Alice\",\"age\":25}\n",
//! "{\"this\":\"is\",\"not\":\"valid\"}\n",
//! "{\"name\":\"Bob\",",
//! "\"age\":35}\r\n"
//! ];
//! let mut ndjson_iter = ndjson_stream::from_iter::<Person, _>(data_blocks);
//!
//! assert_eq!(ndjson_iter.next().unwrap().unwrap(), Person { name: "Alice".into(), age: 25 });
//! assert!(ndjson_iter.next().unwrap().is_err());
//! assert_eq!(ndjson_iter.next().unwrap().unwrap(), Person { name: "Bob".into(), age: 35 });
//! assert!(ndjson_iter.next().is_none());
//! ```
//!
//! # Configuration
//!
//! There are several configuration options available to control how the parser behaves in certain
//! situations. See [NdjsonConfig](config::NdjsonConfig) for more details. To specify the config
//! used for a parser, use the appropriate `_with_config`-suffixed function.
//!
//! In the example below, we use [from_iter_with_config] to construct an NDJSON-iterator which
//! ignores blank lines. That is, it does not produce an output record for any line which consists
//! only of whitespace rather than attempting to parse it and raising a JSON-error.
//!
//! ```
//! use ndjson_stream::config::{EmptyLineHandling, NdjsonConfig};
//! use serde::Deserialize;
//!
//! #[derive(Debug, Deserialize, Eq, PartialEq)]
//! struct Person {
//! name: String,
//! age: u16
//! }
//!
//! let data_blocks = vec![
//! "{\"name\":\"Charlie\",\"age\":32}\n",
//! " \n",
//! "{\"name\":\"Dolores\",\"age\":41}\n"
//! ];
//! let config = NdjsonConfig::default().with_empty_line_handling(EmptyLineHandling::IgnoreBlank);
//! let mut ndjson_iter = ndjson_stream::from_iter_with_config::<Person, _>(data_blocks, config);
//!
//! assert_eq!(ndjson_iter.next().unwrap().unwrap(), Person { name: "Charlie".into(), age: 32 });
//! assert_eq!(ndjson_iter.next().unwrap().unwrap(), Person { name: "Dolores".into(), age: 41 });
//! assert!(ndjson_iter.next().is_none());
//! ```
//!
//! # Fallibility
//!
//! In addition to the ordinary interfaces, there is a fallible counterpart for each one. "Fallible"
//! in this context refers to the input data source - in the examples above the iterator of
//! `data_blocks`.
//!
//! Fallible parsers accept as input a data source which returns [Result]s with some error type and
//! forward potential read errors to the user. See
//! [FallibleNdjsonError](fallible::FallibleNdjsonError) for more details on how the error is
//! communicated.
//!
//! In the example below, we use a fallible iterator.
//!
//! ```
//! use ndjson_stream::fallible::FallibleNdjsonError;
//! use serde::Deserialize;
//!
//! #[derive(Debug, Deserialize, Eq, PartialEq)]
//! struct Person {
//! name: String,
//! age: u16
//! }
//!
//! let data_blocks = vec![
//! Ok("{\"name\":\"Eve\",\"age\":22}\n"),
//! Err("error"),
//! Ok("{\"invalid\":json}\n")
//! ];
//! let mut ndjson_iter = ndjson_stream::from_fallible_iter::<Person, _>(data_blocks);
//!
//! assert_eq!(ndjson_iter.next().unwrap().unwrap(), Person { name: "Eve".into(), age: 22 });
//! assert!(matches!(ndjson_iter.next(), Some(Err(FallibleNdjsonError::InputError("error")))));
//! assert!(matches!(ndjson_iter.next(), Some(Err(FallibleNdjsonError::JsonError(_)))));
//! assert!(ndjson_iter.next().is_none());
//! ```
//!
//! # Crate features
//!
//! * `bytes`: Offers an implementation of [AsBytes](as_bytes::AsBytes) on [Bytes](bytes::Bytes) and
//! [BytesMut](bytes::BytesMut) from the [bytes] crate.
//! * `iter` (default): Enables the [Iterator]-style interface ([from_iter] family).
//! * `stream`: Enables the [Stream](futures::Stream)-style interface from the `futures` crate
//! ([from_stream] family).
pub use cratefrom_iter;
pub use cratefrom_iter_with_config;
pub use cratefrom_fallible_iter;
pub use cratefrom_fallible_iter_with_config;
pub use cratefrom_stream;
pub use cratefrom_stream_with_config;
pub use cratefrom_fallible_stream;
pub use cratefrom_fallible_stream_with_config;
pub