Search Results for "options"

HTTP client for Elixir, based on HTTPotion. HTTPoison uses hackney to execute HTTP requests instead of ibrowse. Using hackney we work only with binaries instead of string lists. First, add HTTPoison to your mix.exs dependencies. Add :httpoison to your applications list if your Elixir version is 1.3 or lower. You can also easily pattern match on the HTTPoison.Response struct. There are a number of supported options(not to be confused with the HTTP options method), documented here, that can...

An Elixir-based built-in error-tracking solution

Guardian is a token based authentication library for use with Elixir applications. Guardian remains a functional system. It integrates with Plug but can be used outside of it. If you're implementing a TCP/UDP protocol directly or want to utilize your authentication via channels in Phoenix, Guardian can work for you. The core currency of authentication in Guardian is the token. By default JSON Web Tokens are supported out of the box but you can use any token that Has the concept of a...

..., also there is a new explain feature - for details see CLI options. If you are planning to use Dialyzer with an application built with the Phoenix Framework, check out the Quickstart wiki. Use dialyxir from the directory of the mix project you want to analyze; a PLT file will be created or updated if required and the project will be automatically compiled.

Ueberauth is a two-phase authentication framework that provides a clear API, allowing for many strategies to be created and shared within the community. It is heavily inspired by Omniauth. You could call it a port but it is significantly different in operation, but almost the same concept. Huge hat tip to Intridea. Ueberauth provides only the initial authentication challenge, (initial OAuth flow, collecting the information from a login form, etc). It does not authenticate each request,...

Pow is a robust, modular, and extendable authentication and user management solution for Phoenix and Plug-based apps. Pow is built to be modular, and easy to configure. The configuration is passed to function calls as well as plug options, and they will take priority over any environment configuration. It's ideal in case you got an umbrella app with multiple separate user domains. The easiest way to use Pow with Phoenix is to use a :otp_app in function calls and set the app environment...

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