Matthieu Napoli

Hey finally coming through the end of my unread email stack ;) I initially went with that but encoding is a special operation of transforming, and doesn't necessarily fit all...

Ohhh I like that idea!

@sagikazarmark :+1: go ahead :)

I'd say at first let's add a new one, and then we'll see if we remove the File one.

:+1: also related: #17

One idea I considered: We currently have `Storage` and `Transformer`. The latter transforms data, without any constraint on input and output (e.g. it can transform to string or to array...

Why not if you want to do it.

The exception stuff is unrelated. But `InvalidArgumentException` would need to extend `StorageException` then (so that user catch it).

Do you have an example?

The idea is that me, as a user, can catch all exceptions of the storage stuff easily: ``` php try { $storage->set('foo', 'bar'); } catch (StorageException $e) { // warn...