tesla
uri_query
Our great sponsors
| tesla | uri_query | |
|---|---|---|
| 4 | - | |
| 1,954 | 13 | |
| 1.3% | - | |
| 7.9 | 5.2 | |
| 7 days ago | 3 months ago | |
| Elixir | Elixir | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tesla
-
Elixir for Cynical Curmudgeons
I haven’t used commanded, exmachina, or ash:
- Tesla has a mode which can be used completely without macros, and I am increasingly encouraging that it be the only way that it is used. So does the author (as of 2020): https://github.com/elixir-tesla/tesla/issues/367#issuecommen...
There is also `req` mentioned in a recent post as an alternative (it looks good, but I am still playing with it to see if it is a suitable replacement for Tesla in all cases).
- Absinthe is something of a compiler itself, because it has to strictly define things the way that is specified in the GraphQL spec. You can now import an SDL file, but you still need to hook resolvers and middleware into it. Honestly, I don’t think that the schema definitions in JS/TS are much better for GraphQL in terms of readability.
Being heavily macro-based means that there are sharp edges that are harder to work around when you want to add your own macros for code reuse purposes. That said, aside from the schema definition, Absinthe is entirely usable without macros. Within the schema definition, Absinthe isn’t making anything up, it’s using the same basic definitions that the GraphQL spec do, adapted for Elixir syntax.
Exmachina didn’t interest me because I don’t think much of factory_bot (which used to be called factory_girl), as I saw it abused far more than used well (IMO, it’s impossible to use correctly). Ash…looks like an interesting experiment, but I don’t know that there’s a lot of pick-up with it compared to Phoenix. And I have yet to find a use for CQRS/ES, so there’s no reason for me to play with commanded. I certainly wouldn’t consider any of these three to be "major" players in Elixir. Tesla and Absinthe? Yes.
-
ElixirのHTTPクライアントでお天気情報を取得したい(2022年)
tesla
- Elixir: Consumindo dados de uma API externa
-
Learn how to deploy Elixir apps on Heroku
To integrate the API via Elixir let's use the HTTP wrapper Tesla. There are many good options out there, such as the good old Httpoison. However, Tesla has some added benefits. I won't go into details as it's not the purpose of this article, but it's worth checking out.
uri_query
We haven't tracked posts mentioning uri_query yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
httpoison - Yet Another HTTP client for Elixir powered by hackney
http_proxy - http proxy with Elixir. wait request with multi port and forward to each URIs
hackney - simple HTTP client in Erlang
bolt - Simple and fast http proxy living in the Erlang VM
httpotion - [Deprecated because ibrowse is not maintained] HTTP client for Elixir (use Tesla please)
mnemonic_slugs - An Elixir library for generating memorable slugs.
Ralitobu.Plug - Elixir Plug for Ralitobu, the Rate Limiter with Token Bucket algorithm
finch - Elixir HTTP client, focused on performance
Maxwell - Maxwell is an HTTP client which support for middleware and multiple adapters.
explode - An easy utility for responding with standard HTTP/JSON error payloads in Plug- and Phoenix-based applications
webdriver - WebDriver client for Elixir.
web_socket - An exploration into a stand-alone library for Plug applications to easily adopt WebSockets.