Open ethanniser opened 8 months ago
currently serialization/deserialization is hard coded in
there are many valid usecase for a user wanting a custom solution:
maybe look at how trpc handles custom transformers?
To discuss: What should the signature of the swappable serializer be? How to handle differences between search param and route param serialization / deserialization?
This should be trivial with @effect/schema but requires a big breaking change
currently serialization/deserialization is hard coded in
there are many valid usecase for a user wanting a custom solution:
maybe look at how trpc handles custom transformers?
To discuss: What should the signature of the swappable serializer be? How to handle differences between search param and route param serialization / deserialization?