Search Results for "encoding"

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...

The Gun library doesn't have a full 2.0 release yet, so we depend on :grcp_gun 2.0.1 for now. This is the same as :gun 2.0.0-rc.2, but Hex doesn't let us depend on RC versions for releases. Generate Elixir code from the proto file as protobuf-elixir shows(especially the gRPC Support section). Implement the server-side code and remember to return the expected message types. You can start the gRPC server as a supervised process. First, add GRPC.Server.Supervisor to your supervision tree.

... 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).