As with issue #2 and #10 one solution would be to allow to insert a custom callback function that could map over attributes, however within the goal of keeping this library simple I don't think that we'll add any such feature before a compelling usecase pops up.
As with issue #2 and #10 one solution would be to allow to insert a custom callback function that could map over attributes, however within the goal of keeping this library simple I don't think that we'll add any such feature before a compelling usecase pops up.
For now I'll close this issue as wont-fix.