Search Results for "decoding"

This library can be configured to handle encoding and decoding requests and responses automatically based on the accept and/or content-type headers. An Elixir OAuth 2.0 Client Library. This library can be configured to handle encoding and decoding requests and responses automatically based on the accept and/or content-type headers. The http client library used is tesla, the default adapter is Httpc, since it comes out of the box with every Erlang instance but you can easily change it to something better.

...It provides straightforward encode and decode functions, along with a protocol-based encoder that lets you customize how your structs become JSON. Developers can derive or implement Poison.Encoder for domain types, control which fields are included, and map complex values into JSON-friendly forms. On the decoding side, it supports options for key handling and flexible parsing of JSON into Elixir maps, lists, and primitive values. Internally it uses optimized binary processing to keep allocations low and throughput high, which is why it became a popular choice in early Elixir ecosystems. The API is intentionally small and unsurprising, making it easy to drop into controllers, background jobs, or data pipelines. ...

...The package can be installed by adding jason to your list of dependencies in mix.exs. Jason follows the JSON spec more strictly, for example, it does not allow unescaped newline characters in JSON strings - e.g. "\"\n\"" will produce a decoding error. No support for decoding into data structures (the as: option). No built-in encoders for MapSet, Range and Stream. No support for encoding arbitrary structs - explicit implementation of the Jason.Encoder protocol is always required. Different pretty-printing customization options (default pretty: true works the same).