Awesome!
hildersantos
Crowdhailer
Creator of Raxx
- I am working on a HTTP server in elixir, GitHub - CrowdHailer/Ace: HTTP web server and client, supports http1 and http2 · GitHub
- Trying to learn about releases, and many infrastructure topics, e.g. docker kuberneties etc.
- working out what it means for elixir applications to be clustered and cloud native
2
sotojuan
I’m working on a site where I’ll post music from around the world—like a blog but organized by country. I’m using it to learn Phoenix!
I’m also always thinking of what libraries and applications I can make.
1
nicbet
I’m working on a Natural Language Processing and Text Summarization library for Elixir:
GitHub - nicbet/essence: Essence is a library for Natural Language Processing and Text Summarization in Elixir. · GitHub | essence | Hex
My pet project is a phoenix-based framework for easier writing of Apple tvOS10 based apps, substituting XHR requests with channels, and extending eex layouts with TVML. No release yet.
2
kpanic
Hey @AstonJ, regarding spacemacs check out the spacemacs ABC series https://www.youtube.com/watch?v=ZFV5EqpZ6_s&list=PLrJ2YN5y27KLhd3yNs2dR8_inqtEiEweE
1
AstonJ
ScrimpyCat
I’ve mostly been working on a stripped down Phoenix app. It’s literally just Phoenix+Ecto+Absinthe (GraphQL), no routes, controllers, views, or channels (although I might have some a bit later, need to think a bit more about it).
Other than that, I’ve been doing a lot of research into Riak and Hibari (I know, not Elixir, but it is still BEAM related). And plan on watching some of the talks from the elixir conf later this week 
.
3
benwilson512
Author of Craft GraphQL APIs in Elixir with Absinthe
Awesome, let me know if you run into any issues. Please try out our v1.2 alpha release, it should be 100% functional we’re just still testing it “in the real world” before releasing beta / RC.
2
ScrimpyCat
Pretty much all went smoothly , only thing I noticed was regarding Absinthe.Plug (v1.2), that it returns different status codes now. These seem more appropriate than the previous ones, although I was unsure if all GraphQL errors are supposed to return 400 or not?
It seems like type errors return 400, but user generated errors do not. Looking at the plug it looks like maybe all GraphQL errors should return 400?
Basically should something like this return 400 or 200 with the new plug?
defmodule Schema do
use Absinthe.Schema
query do
field :test, type: :integer do
resolve fn _, _ ->
{ :error, "blah" }
end
end
end
end
# What Absinthe.Plug v1.2 currently returns:
# curl -i -X POST -H "Content-Type: application/graphql" -d '{ test }' http://localhost:4000
# HTTP/1.1 200 OK
# ...
# {"errors":[{"message":"In field \"test\": blah","locations":[{"line":1,"column":0}]}],"data":{}}
If it is meant to return 400, then it is because the user created error is creating a GraphQL response with a data field. While the plug seems to be matching on each field individually, essentially: {:ok, %{data: _}} followed by {:ok, %{errors: _}}. So simplest fix would be reordering the matches so the :errors match is handled before the :data match.
1