Angelika Tyborska

In the past I have used https://coveralls.io/ + https://github.com/parroty/excoveralls, apparently you can also pass a `--cover` option to `mix test`: ``` $ mix test --include external --cover Cover compiling modules...

> The indenting, I would rather point people to mix format In which way would you point people? From the context I'm guessing NOT by having an analyzer comment? Would...

Added three so far that I was personally sure about. Feel free to add more or dispute specific ones 🙂 https://github.com/exercism/elixir-analyzer/issues/103 https://github.com/exercism/elixir-analyzer/issues/104 https://github.com/exercism/elixir-analyzer/issues/105

@jiegillet I would be fine with an informational comment telling the student to try to remove usages of `IO.inspect` and `IO.puts` after they finished debugging. It is a common problem....

There's a check for two-fer for those but not much else. Using `@spec`, `@moduledoc` and and `@doc` is a personal choice in my opinion. It's definitely helpful in bigger projects,...

I felt comfortable telling everyone about `mix format` when I knew that everyone is using the CLI (and only if their solution was horribly misformatted). Now with the web editor,...

IMO both are too subjective for me to feel comfortable adding them to the analyzer. I agree with you that most two-clause cases should be `if`s instead but not everyone...

Too subjective IMO, and yes, I say that mostly because _I_ never use `map_join` 😇. I don't even know why.

Hi! Thank you for the issue! > They are just the same thing, aren't they? No, not at all. The functions provided in the boilerplate, `filter_by_year` and `filter_by_country`, don't use...

Thank you for the bug report! There's definitely something wrong. The check for the order of `@doc` and `@spec` seems not to handle private functions very well. This code produces...