3 ms·
I've heard more than one person argue against automatically generated encoders/decoders since it's easy to accidentally introduce breaking changes to your API b
by PhineasRex 9y ago
I've heard more than one person argue against automatically generated encoders/decoders since it's easy to accidentally introduce breaking changes to your API by renaming a record field / class method.
If that's your view then Elm's approach is a plus for the language since it eliminates a potential pitfall.
- shakna 9y agoHaskell's way of pre-defining an interface handles that, with less than a quarter of the boilerplate.
- codygman 9y ago> argue against automatically generated encoders/decoders since it's easy to accidentally introduce breaking changes to your API by renaming a record field / class method Can anyone further substantiate this argument, I feel like it's not very strong as is.