Using Facades to Simplify Elixir Modules

Let’s dig into some examples.

There has to be a better way.

It turns out there is a better way. And, like most better ways, it turns out that the solution to our problem is obviously simple.

Now our Chord.Voicing module is entirely concerned with the act of generating chord voicings for a given set of notes.

We can continue on with this pattern by creating a new module to implement each of our features: Chord.Fingering, Chord.Renderer. From there we can flesh our our Chord module to wire our convince functions up to their actual implementations:

Beautiful.

Using the above pattern, we might make a mistake when passing the arguments from our first function head into the function in our implementation module (I’ve done it before).

Thankfully, Elixir gives us a way to prevent this mistake:

Elixir automatically wires each of the delegated functions together, preventing any mindless developer mistakes from creeping into our codebase.

Another less weighty way to thing of Chord is as an “API module”. It’s sole purpose is to act as an “application programming interface” within our application.

What would you call this kind of pattern?

Related posts:

I have a serious disdain for spin offs and most sequels and live action movies that are based on cartoons. Thus, when I started watching the ABC comedy The Kids are Alright, I found everything I was…

OptiMize is a non-profit organization affiliated with the University of Michigan whose mission is to empower students of all ages and backgrounds to ideate and execute entrepreneurial projects that…

CAT stands for common aptitude test. CAT Line Chart is important and useful in logical section. This topic is an integral part of many competitive exams. An aspirants could except few questions from…