Jason Axelson
Jason Axelson
One of the schemas that we use ExJsonSchema to validate has a top-level `anyOf`. When there's an error in this schema, we don't get helpful feedback from `ExJsonSchema.validate`. The error...
I get a warning when I run intialize: ``` iex(1)> IExHistory2.initialize() [info] init got unexpected: {:"ETS-TRANSFER", :ets_history_bindings_local_nonode@nohost, #PID, []} :ok :ok IExHistory2 :ok IExHistory2 version 5.3 is enabled: Current history...
`"~> 1.16.0-otp-26"` is not really a valid version specifier so when I was running on `1.17.3-otp-27` I got an error: ``` ==> iex_history2 warning: the dependency :iex_history2 requires Elixir "~>...
When I work with state machines I value having a state diagram that describes the states and valid transitions.
Some of our backend requests for our integration tests take longer to complete than others so we'd like to be able to control the max timeout before a given condition...
Currently if you open up a path such as `tig ./src` then you see all commits that modified files in that path. So far so good. But if you then...
Small update to the readme for clarity. Fixed a markdown rendering issue. Use more formal language instead of "wanna". Fixed a documented default.
Is there a way to get a listing of all the `writegood-mode` issues (Weasel words, Passive voice, Duplicate words) in a buffer?
Fixes compilation warnings from using the struct update syntax (which now isn't as necessary because of type inference, although it can still be helpful to make the code more readable)...