KEYNOTE: Phoenix 1.3
summary
Phoenix 1.3 actually reorganizes generated apps: it moves web into lib and removes the root-level web folder, adds a top-level assets directory to contain package.json and node_modules, and replaces the vague “model” dump with explicit contexts that define public APIs and data boundaries. Generators now emit context modules, examples use Ecto schemas and Ecto.Multi embedded schemas, and controllers can use action fallbacks to centralize error-to-response handling, all intended to reduce controller boilerplate and encourage isolated, testable components.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:23Phoenix 1.3
- 1:46phoenix.new 1.3
- 4:45phoenix.gen.* = 1.2
- 7:17phoenix.gen.* 1.3
- 11:21RIP web/models
- 13:58Bounded Context
- 16:54Data-centric Schemas
- 19:20Phoenix Umbrella Projects
- 40:09Should I use an umbrella?
related talks
38mIntroduction to the Phoenix Framework
32mWhy I choose Phoenix
01h 00mPhoenix: an Intro to Elixir's Web Framework
40mTaking Off with Phoenix
44mRise of The Phoenix - Building an Elixir Web Framework
33mWhat's Next for Phoenix
45mPhoenix a web framework for the new web
50mPhoenix Framework: a (Truly) Fullstack Stack for Building Real-Time Web