/me coughs:
{Credo.Check.Readability.MaxLineLength, priority: :low, max_length:
120},
On a side note, I use fence blocks in my doctests without issue? Just have
to have a blank line before/after the code itself:
https://github.com/OvermindDL1/permission_ex/blob/master/lib/permission_ex.ex#L78-L86
On Sunday, October 30, 2016 at 2:58:19 PM UTC-6, José Valim wrote:
>
> Alright, I am convinced. :) Please send a PR if you would like to see this
> feature in doctests.
>
>
>
> *José Valim*
> www.plataformatec.com.br
> Skype: jv.ptec
> Founder and Director of R&D
>
> On Sun, Oct 30, 2016 at 8:21 PM, Chris Keele <[email protected]
> <javascript:>> wrote:
>
>> > not using fenced blocks is more readable for those reading the
>> documentation inline
>>
>> This is a good point. In other markdown I've experimented with indenting
>> the block once as a decent compromise between (personal preference in)
>> writability and readability.
>>
>> > Also, can I take the opportunity to do a small rant on the 80 spaces
>> limit?
>>
>> 👏
>>
>> My motives were more to figure out credo, and get the noise down to see
>> more meaningful complaints. I've figured out how to customize and filter it
>> now, so I'm satisfied with a wider margin.
>>
>> > The omission is somewhat intentional
>>
>> It still does feel... incongruent to me that you can author docs the way
>> you want, publish them with ExDoc, and have a build fail because ExUnit
>> doesn't care for fenced code blocks.
>>
>> Running doctests should take backseat to writing good docs. I feel like
>> ExUnit should support the full range of ExDoc code blocks, aesthetics
>> aside. If ExDoc didn't support them, I'd feel differently.
>>
>> > as nobody has a strong usecase for it
>>
>> I'm lukewarmer on this than I was, after some thought, but I'd probably
>> use it in moduledocs and the consistency angle seems important to me.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "elixir-lang-core" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elixir-lang-core/70EE4DDB-1E87-4236-952A-795B9B5E12DF%40chriskeele.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elixir-lang-core/186053d3-d037-44bb-b3f9-cc0ba2cfa982%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
