Curiosum is a blog for curious people There are two of us - myself and Michał. We mostly write about Elixir programming, but not only. This is our first post, let us know what you think!
Handling dependencies is a pretty basic topic, however pretty confusing when you start your journey with a programming language. I’ve done my best to cover how it’s done in Elixir.
This is the beginning of a series of tutorials where Michał will show you step by step how to create an application (based on Phoenix LiveView) similar to the Messenger app we are all familiar with.
If you want to be up-to-date you can sign up to the newsletter or push notifications
Metaprogramming sounds scary, but in Elixir you don’t need supernatural powers to use it to great success - find out how, why and when to do this. Plus, there are practical examples of what macros can actually help you with!
Let us know whether you like it, and do subscribe to our newsletter or push notifications!
Hello again, we’ve published another episode of our Modern Talking with Elixir series - this time we’re actually bootstrapping our Phoenix LiveView app with a database structure for a Messenger app, and creating our initial LiveView page.
We appreciate your feedback, and - as always - please subscribe to follow us
You could move the :cache_store_backend option to the config rather than having it at the endpoint, but I definitely prefer to have most of the config as close as possible to the relevant code rather than in the app env. This may have been the intention, but wasn’t clear to me.
Pow by default assigns:current_user to the conn, so you only need a plug that can preload what’s needed. That plug would essentially be the same as the current one though, but the description of makes it sound like :current_user isn’t assigned by default.