# The future of serialization & deserialization APIs

**URL:** <https://forums.swift.org/t/the-future-of-serialization-deserialization-apis/78585>\
**Category:** Discussion\
**Tags:** foundation, codable, macros\
**Created:** [March 17, 2025, 8:25pm UTC](https://forums.swift.org/t/the-future-of-serialization-deserialization-apis/78585 "2025-03-17T20:25:29Z")\
**Posts on this page:** 1\
**Showing post:** 95

<div class="post-metadata">

**Author:** ![mickeyl](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mickeyl/32/12258_2.png) [@mickeyl](https://forums.swift.org/u/mickeyl)\
**Post date:** [March 24, 2025, 10:18am UTC](https://forums.swift.org/t/the-future-of-serialization-deserialization-apis/78585/95 "2025-03-24T10:18:02Z")

</div>

Agreed. I'm using code based on [GitHub - gonzalezreal/DefaultCodable: A convenient way to handle default values with Swift Codable types](https://github.com/gonzalezreal/DefaultCodable) ­which comes up with a set of property wrappers that make Codable handle more cases. Also, some glue logic to deal better with optionals based on [https://forums.swift.org/t/using-property-wrappers-with-codable/](https://forums.swift.org/t/using-property-wrappers-with-codable/).

A new system should, at the minimum, provide all that builtin.

---

_[View the full topic](https://forums.swift.org/t/the-future-of-serialization-deserialization-apis/78585)._