It’s the difference between validation errors and execution errors. v1.2 is a lot more strict about how it handles errors. If there are any validation errors it will refuse to execute at all since we can now do full document validation prior to any execution. Those errors by convention also will give you a 400.
User errors happen during execution. A 400 would be the wrong response because it isn’t a “bad request”, since we’re able to execute it.
I’m porting this library to Elixir:
https://github.com/sindresorhus/boxen
Mostly for fun! Learning a lot about strings and Unicode.
Building the administration interface for some HTTP services actively used at the company I work for.
ngw
Ecto even easierexprotobuf to work with Protobuf v2
Just finished deploying a test app with edeliver and disillery to set the stage for releasing my first production Elixir app.
These days I’ve been using a few hours building a tiny concatenative language Rex on top of Elixir syntax, still very very experimental, but would like to experiment with the idea of tacit programming in elixir. Also have a few tiny libs I mostly use at my day-work (also elixir based) happy_with, pit, params
Also not Elixir specific but Erlang-related is my current work in progress alpha as hell Elm compiler to erlang’s beam vm: Elmer keep-it-secret
These days I:
While still getting my footing in Elixir, I already POC-ed to my folks at work how much easier is getting multiple responses from an (internal) API responding with XML docuemnts is in Elixir than in Python.
On the “real world” front, finishing on “Introduction to Elixir” (I think is the name of the book) and will graduate to “The little Elixir & OTP book” after which… the plan is to baby-step more stuff internally at work. Probably won’t cause a shift… there’s too much Python code on production, but, maybe for newer projects…
Pit is amazing! I was looking for something like this and gave up, thinking that I had to create it myself. Definitely going to use it!
