This is the same utility but in a very different language. It’s not quite as polished as the Node version (but won’t take long to catch up).
Issues that I have had during the port:
My machine had a very old erlang implementation (I had installed this when reading the Erlang chapter of 7 languages in 7 weeks – over 7 years ago) which broke HTTPoison, a fairly common HTTP library. The errors pointed to HTTPoison not working on a windows machine (which I have found to not be true).
The Contentful Elixir bindings are not very advanced. They don’t return the total number of items that you are paging through. It was not difficult to use the api directly.
There are lots of Elixir bindings for Neo4j. Very few of them are clearly documented for writing to Neo4j. Eventually I landed on bolt_sips. Bolt is too primitive, neo4j_sips uses a very old version of HTTPoison.
The Elixir error messages are incredibly clear.
Credo is great for ensuring best practices are applied.
Functional programming allows you to test real code without mocks or spend time fighting promises.
iex is a great REPL environment. You can recompile a module and carry on without restarting everything.
The code is self documenting. This is the top level method:
VSCode is a great editor for elixir. It’s great from the command line
The above will open vscode on the project in the current directory.