# Customizing Hash

**URL:** <https://discourse.dry-rb.org/t/customizing-hash/1200>\
**Category:** dry-types\
**Created:** [February 9, 2021, 7:37pm UTC](https://discourse.dry-rb.org/t/customizing-hash/1200 "2021-02-09T19:37:09Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![solnic](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.dry-rb.org/solnic/32/779_2.png) [@solnic](https://discourse.dry-rb.org/u/solnic)\
**Post date:** [February 12, 2021, 6:03am UTC](https://discourse.dry-rb.org/t/customizing-hash/1200/3 "2021-02-12T06:03:32Z")

</div>

I don’t recommend using dry-types for parsing/preprocessing/mapping data. I know it’s tempting to do due to flexibility of the types, and it even may work well in various cases, but it’s not a dedicated solution so you may hit a wall or end up with too complicated code. You _especially_ should not use dry-struct with complex dry-types for complex mappings. Again, you can get away this if things are simple but it’s not the right abstraction.

We just had a short convo about this in [this thread](https://discourse.dry-rb.org/t/dry-struct-dependent-attributes/1191).

I feel like we should finally come up with a nice solution. There’s dry-transformer that you could evaluate too. It’ll become a generic data mapping solution eventually that works well with dry-types. I’ll be working on this _for sure_ later this year because rom 6.0 will use it under the hood.

---

_[View the full topic](https://discourse.dry-rb.org/t/customizing-hash/1200)._