Christopher Adams

Here's a rule that differs and so we should consider: [always use parens for defs even if they have no arguments](https://github.com/lexmag/elixir-style-guide/blob/master/README.md#fun-parens).

@DavidAntaramian the rule in this guide says to omit parens if the `def` has no arguments.

I'm interested in the justification/rationale idea. Here's how I think we can move this forward: * grep all the rule links and put them on a wiki page, maybe with...

Given that the formatter enforces blank lines between multiline `def`s, the style conventions could be reworded as: 1. Don't separate single-line `def`s of the same function with blank lines. 2....

> Is there a way for us Elixir devs to use this style guide in an automated way? It should be possible to write custom Credo checks for many of...

@sergiotapia You already mentioned atom-credo. That runs `mix credo` and reports the output, right? In theory it should work with a customized Credo config. It would be a fair amount...

> I have created [rrrene/credo#933](https://github.com/rrrene/credo/pull/933) to enforce https://github.com/christopheradams/elixir_style_guide#pipe-operator tada This is great work @Stratus3D, please keep us up to date on your credo PRs.

Things do get tricky with macros, but this guide can't anticipate how every library's macros should be laid out. In the case of Ecto, I'd follow their documentation or other...

Great suggestion. I think this would be appropriate as an additional rule after https://github.com/christopheradams/elixir_style_guide#module-name-nesting. The example could be something like `MyApp.XmlParser` for `my_app/parsers/xml_parser.ex`. Could we say more about when this...

"Readability" can be subjective. Can you think of some examples that would illustrate the guideline? Also, I'd probably phrase this in terms of anonymous functions rather than lambdas, to keep...