Nicd
I needed a way to get the GitHub colours for programming languages based on their name (as in the colours used in the bars that show how much of each language a project has) so I wrote a small library for it. You can find it at language_colours | Hex
I also wanted to learn how to structure a library to be configurable so it’s a bit overkill in that regard but should be simple to use. It has support for a fallback in case the language is not found, using the Rainbow package.
Actually currently I have an issue with the 1.0.0. It has a mix task that lets you download the colour data. This task uses httpc and thus it uses inets also. When compiling, it complains that the current project doesn’t have inets in the applications list. But it’s only used in this task so I don’t think it should be there at all. How should I get rid of this message?
Where Next?
Trending in Announcing
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
03juan
This Elixir v1.11 release note on Compiler checks: application boundaries should help.
Nicd
Thanks, I’m aware of that. My issue is that the task is not part of the library code. I.e. the task will not be present when the code is compiled to a release, it is only there for development. Thus I don’t want to add
:inetstoextra_applications, which would presumably affect the deployed release.I got advice from José to use the xref trick to suppress the warning. It’ll hide any warnings about
:inets, but I guess I’ll have to live with that.03juan
Fair enough, coming from José I guess that’s all one can do… Sorry for necroing the thread.
For what it’s worth I’ve learned some good things related to configuration and dependency injection from your code. Thank you.
Nicd
There’s nothing to apologise for.
And thanks for your kind words.
This is my first proper library that has configuration, so don’t take it too much as gospel.
But I think it’s pretty good, though I like to use maps and structs instead of keyword lists in configuration and supervisor arguments, so that’s somewhat unusual in Elixir.
03juan
Yes, I did note of the map interface and I’m also partial to that; probably a remnant of my Ruby days.
Always good to see how others implement things even if it’s not necessarily “the done way”, can always learn something when I’m sitting in the butt-end of the world without personal mentors.