codee 0.2.0

Easy and flexible way of encoding and decoding data into either strings or bytes
Documentation 
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

# Codee

[![Crates.io](https://img.shields.io/crates/v/codee.svg)](https://crates.io/crates/codee)
[![Docs](https://docs.rs/codee/badge.svg)](https://docs.rs/codee/)
[![MIT/Apache 2.0](https://img.shields.io/badge/license-MIT%2FApache-blue.svg)](https://github.com/synphonyte/codee#license)
[![Build Status](https://github.com/synphonyte/codee/actions/workflows/ci.yml/badge.svg)](https://github.com/synphonyte/codee/actions/workflows/ci.yml)

Easy and flexible way of encoding and decoding data into either strings or bytes.

This crate provides generic traits for `Encoder`s and `Decoder`s as well as several
implementations for commonly used (de)serializer crates.
    
This makes it easily possible to abstract away the serialization and deserialization independent
of the concrete crate used. You can write a function like this:

```rust
use codee::{CodecError, Decoder, Encoder};

fn store_value<T, Codec>(value: T) -> Result<(), CodecError<<Codec as Encoder<T>>::Error, <Codec as Decoder<T>>::Error>>
where
    Codec: Encoder<T, Encoded = String> + Decoder<T, Encoded = str>,
{
    let encoded = Codec::encode(&value).map_err(CodecError::Encode)?;
    let decoded = Codec::decode(&encoded).map_err(CodecError::Decode)?;

    Ok(())
}

// Then we can use it like this:

use codee::string::{JsonSerdeCodec, FromToStringCodec};

#[derive(serde::Serialize, serde::Deserialize)]
struct MyStruct {
    field: usize,
}

store_value::<i32, FromToStringCodec>(42);
store_value::<MyStruct, JsonSerdeCodec>(MyStruct { field: 42 });
```