Stream: API design

Topic: HttpDecodingFailed


view this post on Zulip Fábio Beirão (Nov 26 2024 at 08:18):

Hello everyone. It's been a while since I used roc. So much progress has happened in the meanwhile. Nothing short of impressive. I was watching Richard's "Introduction to Roc Programming Language", and the http error (on the client side) is nothing short of impressive. However, coming from Elm decoders, I found it super strange that the HttpDecodingFailed does not have a payload with the actual error "Expected to find a string with name 'message'" or something. I am sure there is some technical decision/limitation behind this. I tried searching Zulip for "HttpDecodingFailed" but I didn't get a single hit (:interrobang:), so that is why I am asking here if the reason for the lack of payload is due to a technical limitation, of if this is something that has been planned for future versions of the API.

view this post on Zulip Kilian Vounckx (Nov 26 2024 at 08:59):

Iirc, there are plans to change the Decode and Encode abilities to allow for custom errors and stuff like that, so it will be possible in the future. Not sure though


Last updated: Jul 06 2025 at 12:14 UTC