Roberts Guļāns
Roberts Guļāns
Main changes: - commands are created with `ExConstructor` (similarly how its done with events `new/1`) without validation and any casting at that point - commands have validate function which takes...
## Feature goal Extend `fl-contains` to mach on children text as well. ```elixir "Some" |> Floki.parse_document!() |> Floki.find("div:fl-contains('Some')") |> IO.inspect(label: :first) # Output: first: [{"div", [], ["Some"]}] "Some" |> Floki.parse_document!()...
Concrete use-case: pagination. There might be other use cases as well. For more feature proof solution part after querying also should be extracted to separate function that can be overwritten....
Following the example in docs, I created a module ```elixir defmodule Id do import Algae defdata any() end ``` when I try to call `Id.new("random value")` i get following error:...
`setup_all` -> should initialize test file scope `setup` -> should be able to setup `scenario`, alternative to background. How they should be behaving together?
It seems that SemaPhoreCI doesn't provide such functionality, or I didn't find it. TravisCI on the other had [does](https://docs.travis-ci.com/user/languages/elixir/). In either case, not selected CI is important, but in fact,...
Registering `tag` specific setup callbacks currently is outside of `ExUnit` default flow. `setup_all` -> setup for test as a whole `setup` -> setup for each test case in file (in...