absinthe_plug alternatives and similar packages
Based on the "Framework Components" category.
Alternatively, view absinthe_plug alternatives based on common mentions on social networks and blogs.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
dayron
A repository `similar` to Ecto.Repo that maps to an underlying http client, sending requests to an external rest api instead of a database -
rummage_phoenix
Full Phoenix Support for Rummage. It can be used for searching, sorting and paginating collections in phoenix. -
phoenix_token_auth
Token authentication solution for Phoenix. Useful for APIs for e.g. single page apps. -
-
-
-
-
-
-
-
-
access pass
provides a full user authentication experience for an API. Includes login,logout,register,forgot password, forgot username, confirmation email and all that other good stuff. Includes plug for checking for authenticated users and macro for generating the required routes. -
-
Votex
Implements vote / like / follow functionality for Ecto models in Elixir. Inspired from Acts as Votable gem in Ruby on Rails -
plug_canonical_host
PlugCanonicalHost ensures that all requests are served by a single canonical host. -
trailing_format_plug
An elixir plug to support legacy APIs that use a rails-like trailing format: http://api.dev/resources.json -
-
CodeRabbit: AI Code Reviews for Developers
Do you think we are missing an alternative of absinthe_plug or a related project?
README
Absinthe.Plug
Plug support for Absinthe, the GraphQL toolkit for Elixir.
Please see the website at http://absinthe-graphql.org.
Installation
Install from Hex.pm:
def deps do
[{:absinthe_plug, "~> 1.5"}]
end
Note: Absinthe.Plug requires Elixir 1.10 or higher.
Absinthe.Plug also requires a JSON codec. Jason and Poison work out of the box.
def deps do
[
...,
{:absinthe_plug, "~> 1.5"},
{:jason, "~> 1.0"}
]
end
Upgrading
See [CHANGELOG](./CHANGELOG.md) for upgrade steps between versions.
You may want to look for the specific upgrade guide in the Absinthe documentation.
Documentation
See "Usage," below, for basic usage information and links to specific resources.
- Absinthe.Plug hexdocs.
- For the tutorial, guides, and general information about Absinthe-related projects, see http://absinthe-graphql.org.
Related Projects
See the GitHub organization.
Usage
In your MyAppWeb.Router module add:
plug Plug.Parsers,
parsers: [:urlencoded, :multipart, :json, Absinthe.Plug.Parser],
pass: ["*/*"],
json_decoder: Jason
plug Absinthe.Plug,
schema: MyAppWeb.Schema
If you want Absinthe.Plug to serve only a particular route, configure your
MyAppWeb.Router like:
plug Plug.Parsers,
parsers: [:urlencoded, :multipart, :json, Absinthe.Plug.Parser],
pass: ["*/*"],
json_decoder: Jason
forward "/api",
to: Absinthe.Plug,
init_opts: [schema: MyAppWeb.Schema]
For more information, see the API documentation for Absinthe.Plug.
Phoenix.Router
If you are using Phoenix.Router, forward expects different arguments:
Plug.Router
forward "/graphiql",
to: Absinthe.Plug.GraphiQL,
init_opts: [
schema: MyAppWeb.Schema,
interface: :simple
]
Phoenix.Router
forward "/graphiql",
Absinthe.Plug.GraphiQL,
schema: MyAppWeb.Schema,
interface: :simple
For more information see Phoenix.Router.forward/4.
GraphiQL
To add support for a GraphiQL interface, add a configuration for
Absinthe.Plug.GraphiQL:
forward "/graphiql",
to: Absinthe.Plug.GraphiQL,
init_opts: [schema: MyAppWeb.Schema]
See the API documentation for Absinthe.Plug.GraphiQL for more information.
Community
The project is under constant improvement by a growing list of
contributors, and your feedback is important. Please join us in Slack
(#absinthe-graphql under the Elixir Slack account) or the Elixir Forum
(tagged absinthe).
Please remember that all interactions in our official spaces follow our [Code of Conduct](./CODE_OF_CONDUCT.md).
Contributing
Please follow [contribution guide](./CONTRIBUTING.md).
License
See [LICENSE.md](./LICENSE.md).
*Note that all licence references and agreements mentioned in the absinthe_plug README section above
are relevant to that project's source code only.