Hey! Why yet another JSON serialization library? We already have SuperJSON, right?
Yes. And SuperJSON is great; I use it a lot. However, things got tricky for me when I had really complex data types, covered with many model classes, often deeply nested and referencing each other, where I needed to serialize it all from/to JSON and save it on the disk. I had to essentially maintain two formats of my data - "serializable data" and TypeScript classes matching this data. It was quite a pain.
I've tried to solve it with modern decorators, making the entire process more declarative and having way less boilerplate.
Very loosely. Swift Codable doesn't require you to annotate every field for example.
happytoexplain•2mo ago
Capturing types in the JSON means you need this tool at both ends. E.g. you couldn't use this to serialize data to send to a typical web API. Is there no way to use TS to declare the type at decode time, like you would in Swift and other strongly typed languages? I'm not super familiar with TS.
pie6k•3mo ago
Yes. And SuperJSON is great; I use it a lot. However, things got tricky for me when I had really complex data types, covered with many model classes, often deeply nested and referencing each other, where I needed to serialize it all from/to JSON and save it on the disk. I had to essentially maintain two formats of my data - "serializable data" and TypeScript classes matching this data. It was quite a pain.
I've tried to solve it with modern decorators, making the entire process more declarative and having way less boilerplate.
Happy to hear your feedback!
Interactive playground - https://codableslib.com/playground Github: https://github.com/pie6k/codables