Provide pipeline-based message decorator #41
You mean something like this? :)
I removed that again, because it seemed a bit overkill to me, but I think it makes sense in a few more ways (like providing information to the UI which fields were changed/added/deleted/what their former content was etc., so it is transparent/switchable in the ui), but I kept this out of the first implementation to prevent it getting too complex and evolve it instead.
Yeah, I think we need to unify the decorators to make the UI more usable.
For the alpha I could live with leaving it like it is implemented now, but for a final I would vote for changing it.