Phillip Davis

That's odd; I would've sworn this passed ```cargo test``` locally. Will investigate.

Sorry I haven't been able to dig deep. Just to record what I have found: I can confirm that the tests pass when running a Meilisearch instance on localhost and...

> @phdavis1027 I think your branch is failing only in the CI because this package only supports Meilisearch v0.27. And the CI is trying to run it against the v0.28....

I am interested by your comment that performance intensive code would be better served using Reader/Writer APIs rather than Serde. I have been using Serde for speed of development but...

Upon thinking about it, this might be best. For any text-based serialization format like UTF-8 buffering probably is more efficient. That said, it's not inconceivable others might have weird usescases...

Based on the top-level crate docs, I think this refers to the split between manual serialization/deserialization via Reader/Writer APIs on the one hand, and the serde API on the other....

Oh interesting. I suppose I assumed that `Text` events only occurred in the context of something like `...`, but debugging does seem to show that they're appearing in `` contexts...

Turns out I missed `write_indent`, which is what caused the fuzz to fail. Fixed that and also added a changelog entry, although I'm not sure I got it in the...

Actually the fuzzer has caught a harder case -- `write_text_content` already has a non-empty type for its result. First thought that jumps to mind is to just return a `Result

> About the original purpose - are you serializing the XML out to a buffer first? If so, wouldn't it be easier to just get the length of the data...