Lessons From Using Phoenix 1.3
[WARNING] I like contexts. Phew… I just wanted to admit that up front. Now that I got that out of the way, I am going to share my journey about using Phoenix 1.3.0 and contexts. My context Lessons: Don’t use the generators Embrace the domain vocabulary Avoid the bloat Consider before umbrellas You should give it a shot Experience I worked on a greenfield project and had an opportunity to use Phoen
Simple Phoenix Text Inputs with Formulator
<%= input form, :email_address, as: :email %> <%= input form, :first_name %> <%= input form, :last_name %> Platformatec has a great post about dynamic forms with Phoenix that teaches developers how to extract some common steps out to their own functions. This is helpful because developers can skip the tedious parts that they tend to repeat, which also helps keep style consistent across a larger fr
Elixir: the new wave or an elegant niche? | HackerNoon
Too Long; Didn't ReadLike a man down on his luck and coming across an old-fashioned church revival tent, I was primed to be baptized. Like a man down on his luck and coming across an old-fashioned church revival tent, I was primed to be baptized. The concise, clear language syntax. The productivity. A charismatic, foreign leader. He even drives race cars — how exotic! I came across Ruby on Rails w
Senior Product Strategy, Design, and Development services for web apps, mobile apps, and websites. | thoughtbot
Our thoughtbot Teams have tailored expertise in the projects, challenges, and skills associated with your business and product at every product stage. We are equipped to partner with teams around the world with our fully-remote delivery model. Rapid validation and early product strategyBuilding a new product and roadmap planningTeam augmentation and process improvementDevOps, Cloud, CI/CD
Elixir for Rubyists
Some aspects look different at a first glance. For example, Elixir code looks a bit more verbose than Ruby code. Module names are spelled out in most function calls. Modules being used in the current file are explicitly included. State is passed into functions as arguments. Before explaining how macros can extend the language, its documentation page explicitly discourages its use. Elixir can indee
Building and testing a Phoenix JSON API
Note: This blog post is for Phoenix 1.2. If you’re on Phoenix >= 1.3 check out the Phoenix guides. Since writing the first version of this guide a lot has changed in Phoenix. In this post we’ll show you how to build and test the index and show actions of a JSON API with Phoenix 1.2. We’ll show you some new techniques we’ve learned since the last time. You’ll learn: How to use the built-in Phoenix
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Better domain modeling in Elixir with sum types
Long-lived processes in Elixir
Organize your functional code
Querying an Embedded Map in PostgreSQL with Ecto
Why Ecto's Way of Storing Embedded Lists of Maps Makes Querying Hard
Playing with Sockets and Processes in Elixir
Testing Random Data in Emails with Bamboo
ExMachina 2.0 - Cast Away
Preloading Nested Associations with Ecto
"Tell, Don't Ask" in Elixir: A Story of Pattern-Matching
An Introduction to the Actor Model - Thoughts & Bots
Elixir for Rubyists (Tute)
45: Derek Prior - From Rails to Phoenix
Make Phoenix Even Faster with a GenServer-backed Key Value Store