Phoenix Contexts - learning resources

[AstonJ]

Wonder if we can compile a list of learning resources, blog posts, talks, threads etc to help those who are just learning about Contexts.

This is a wiki - so please add anything you feel is missing…

What are Phoenix Contexts?

In short:

Phoenix Contexts are just dedicated modules that expose and group functionality.

In depth:

• Official docs
• Phoenix Contexts explained by forum members
• Chris’s announcement on 1.3rc
• Chris’s announcement on 1.3 RC3 release

Books

Programming Phoenix - due to be updated for Phoenix 1.3.

Screencasts

Phoenix Contexts Screencast

I did an episode on Phoenix contexts. This is a good episode for anyone new to Phoenix or wanting to see how contexts work. https://elixircasts.io/phoenix-contexts

Talks

Lonestar ElixirConf 2017 - KEYNOTE: Phoenix 1.3 by Chris McCord

Chris McCord | Keynote: Phoenix - Gauging Progress

ElixirConf 2017 - Closing Keynote - Chris McCord

ElixirDaze 2018 - Building beautiful systems with Phoenix contexts... by Andrew Hao

Blog Posts

Putting Contexts in Context | Michał Muskała

https://panache.nu/blog/giving-phoenix-contexts-some-context

https://blog.jakewilkins.com/2017/06/23/working-with-phoenix-1-3-directory-structure-a-love-story/?utm_content=buffer4c74b&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer

http://www.resurgens.io/2017/06/26/phoenix-1-3.html by @dlively (thread)

Authorization Considerations For Phoenix Contexts - DockYard

Lessons From Using Phoenix 1.3

Understanding the concept of a context in Phoenix (2017-08-16)

Threads

Phoenix v1.3.0-rc.0 released

As promised, the first release candidate of Phoenix 1.3.0 is out! This release focuses on code generators with improved project structure, first class umbrella project support, and scaffolding that re-enforces phoenix as a web-interface to your greater Elixir application. We have also included a new action_fallback feature in Phoenix.Controller that allows you to translate common datastructures in your domain to valid responses. In practice, this cleans up your controller code and gives you a si…

How to determine contexts with Phoenix 1.3

I am just trying to migrate my project to Phoenix 1.3 with new contexts mechanism. But I am not sure how I should split my schemas into this contexts. I read a lot about DDD and UL/Bounded Contexts in last few days, but all examples using something like large ERP systems. Also in DDD contexts used to “namespace” UL (ubiquitous language) within this contexts like Sales/Support/Analytics, etc. where Product will be used. At other side @chrismccord used blog (post, comments) example in his ElixirC…

How context should be used in phoenix 1.3?

Hi, I have trouble understand how context should be used. Let say that I run : > mix phx.gen.html Accounts User users email:string:unique password_hash:string is_admin:boolean This will create the User structure under the Accounts context, which means that it will create 2 files, accounts.ex and user.ex. My question is what kind of function should be put respectively in account.ex, and in user.ex ? Let say for exemple that I want to hash the password while registration. With the previous v…

Contexts? How can I figure out mine?

Hi everyone As all of you might know, Phoenix 1.3 comes with a new folder structure and introduces contexts/ API boundaries. I’m now trying to move my application to 1.3.0-rc.0, but I have some problems to find my contexts. I can see how it works for simple things like a blog, but as soon as things get more complicated, I’m lost. I’ve searched the web a bit, but couldn’t find anything helpful. My application will be used by two groups of users, and I might eventually split it in…

Understanding contexts in Phoenix 1.3

I think the new structure and general advise around contexts in 1.3 is excellent. Putting persistence behind functional interfaces really makes sense to me. I’d like to understand contexts a little more for this use case: In 1.2 I had three models (as well as other standard account/user type functionality). App.Competition # has_many :games App.Team # has_many :games App.Game # belongs_to :team, :competition Now thinking in terms of contexts I was going to go with a kind of top level context …

Contexts and auth

I’m building an app in Phoenix 1.3 and I’m struggling with decisions related to contexts. Specifically, I don’t understand how user schemas in multiple contexts should interact with auth. I’m using Guardian for authentication and overriding controller __action__ to pipe around my current_user to my controller actions as an additional argument. def new(conn, params, current_user) do end Above, current_user is fetched from Guardian and loaded into assigns using a router plug. When I started wr…

And more:

https://elixirforum.com/search?q=contexts

Misc

• Phoenix 1.3 Sample Application (with Absinthe)