trivelop @rrrene on

ElixirConf.EU: The roof is on fire!

I had the pleasure to give a talk about Credo at this year's ElixirConf.EU in Berlin. It was an amazing experience, with the first day culminating in a memorable rooftop party with old and new #elixirfriends.

Thank you all for two fantastic days full of interesting discussions and great talks (and lightning talks, oh my ... I was really sad they were only 5 minutes long and at the same time impressed how much the speakers put into that short timeframe). The hallways were filled with equal levels of laughter, excitement and humble levels of strong confidence.

Everything that impressed me about this community online is even more impactful in person. As the adrenalyn is slowly wearing off, I try to sort all these impressions and new ideas in my head. Just one thing is crystal already: I can't wait to meet even more of you nice people in September!

P.S.: The slides of my talk are now on SpeakerDeck as well:


Credo: Introducing Lint attributes

I just released v0.3.3 of Credo, a static analysis tool for the Elixir language.

With the v0.3.0 release we finally introduced support for per-function exclusion of checks. This has been a community requested feature since the very beginning and I am happy to announce: it's finally here.

I was opposed to "magic comments" like # credo: <check-name>:off, since they would clutter your code, be very tool-specific and not very "Elixirish".

As it turns out the solution was quiet easy: Let's use a module attribute like @doc, which also contains code-relevant information which is often written in comments in other environments. Building on this idea, Credo now let's you use a module attribute named @lint to configure linting for specific functions.

@lint attributes let you exclude specific functions completely:

# Case 1: don't lint anything inside `my_fun`

@lint false
def my_fun do
end

In my mind, this reads just right. Given that you should use these function-specific exclusion rarely, it clearly communicates intention and does not clutter your code. But say you have a function where a specific check fails, but you know that this is an instance where you are fine with it. You can now mark that function to ignore all issues generated by that particular check (using the same syntax used in the config file):

# Case 2: don't run the TagTODO check inside `my_fun`

@lint {Credo.Check.Design.TagTODO, false}
def my_fun do
end

To exclude more than one check, e.g. a whole category of checks, you can use a Regex instead of the check module:

# Case 3: don't run any Refactor checks inside `my_fun`

@lint {~r/Refactor/, false}
def my_fun do
end

Finally, you can supply multiple tuples as a list and combine all of the above:

# Case 4: combine the above

@lint [{Credo.Check.Design.TagTODO, false}, {~r/Refactor/, false}]
def my_fun do
end

I hope you enjoy this release as much as I do. Thanks to all your feedback, we're already at v0.3.3.

You can check out Credo on GitHub.


Elixir Carnival

Right now there is a yearly celebration taking place where I live called "Fasching" or simply "Carnival". People dress up as all kinds of persons, like pirates, tussis, sailors or ladybug couple with an age difference. I know, Germans, right? ;-)

In a way this coming week is also going to be my personal "Elixir Carnival" as I plan to dress up to look like a serious member of the Open Source community, release a bunch of software and even give a talk about it in the end.

I would like to share this now, because I owe all of this to a very supportive and welcoming community of fellow Alchemists, but there will hardly be time to write an appropriate blog post next week.

So, here we go:

  • Monday The @elixirstatus Twitter account should pass the 1,000 follower mark around this date. The steady growth of this community makes me really happy.
  • Tuesday Credo will see its v0.3.0 release around Tuesday, introducing new checks, UI improvements and the @lint attribute to its analysis (preliminary CHANGELOG here). As with ElixirStatus, I can't describe how glad I am that this project is so well received.
  • Thursday I am really excited to give my first Elixir talk at ElixirRuhr on Thursday. It will be titled "Good Tooling educates" and I will upload the slides to SpeakerDeck after the event!
  • Friday And finally HexFaktor - an upcoming service to monitor your projects' Hex deps - is scheduled to start in private beta at the end of the week. My gut tells me this will be in private beta for a couple of weeks to ensure everything runs smoothly. You can register for the beta on hexfaktor.org.

Since there are things like day job emergencies and family life to account for, some of these might happen a day later, but the above represents the overall plan for the week.

Let me finish with the original intent of this post: Saying Thank you! to everyone who has been along for the ride. I could not imagine more fulfilling side projects and both the Elixir and Ruby communities have been so supportive over the last 2 years. It really means something to me.

Thank you!

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


Fork me on GitHub