https://mariano-gonzalez.com/tags/object-mapping/ Recent content in Object-Mapping on Mariano Gonzalez Hugo en-us <p>Copyright © 2026 Mariano Gonzalez</p><p xmlns:dct='http://purl.org/dc/terms/' xmlns:cc='http://creativecommons.org/ns#' class='license-text'><a rel='cc:attributionURL' property='dct:title' href='https://github.com/eschizoid/eschizoid.github.io/tree/main/content'>Content</a> licensed under <a rel='license' href='https://creativecommons.org/licenses/by/4.0'>CC BY 4.0</a></p> Mon, 22 Jun 2026 00:00:00 +0000 https://mariano-gonzalez.com/posts/post-7/ Mon, 22 Jun 2026 00:00:00 +0000 https://mariano-gonzalez.com/posts/post-7/ <p><p class="md__image"> <img src="logo.png" alt="telescope" /> </p></p> <h2 id="the-setup">The setup</h2> <p>Mapping one Java object to another is routine work in most apps, and <a href="https://mapstruct.org/">MapStruct</a>, the standard tool for it, still has you name each field with a string: <code>@Mapping(source = &quot;customerName&quot;, target = &quot;fullName&quot;)</code>. Those two names are what the whole mapping turns on, and they are strings: rename the field, and they stay exactly as they were.</p> <p>MapStruct earned its place. Ten years, a huge adopter base, a bug list that converged long ago, and it generates genuinely fast code; I reach for it too. Those strings are just the one piece of its 2014 design that aged badly.</p>