How do we associate different contexts like say user has a account( Account context) and has many orders( Order context).
pra
sabondano
@wojtekmach I was wondering what your thoughts are regarding “not respecting” the context boundary as explained on some of the replies above? For example, I see that in hexpm (https://github.com/hexpm/hexpm49) you don’t have an accounts.ex file and the controllers reach directly into modules within the context boundary (e.g. UserController reaches into Hexpm.Accounts.User which crosses the “Accounts” context boundary). It seems to me that the phoenix core team is trying to encourage the community to “respect the context boundaries” but looking at hexpm I’m wondering if I’m missing something. Any thoughts you can share with me on this topic would be very appreciated. 
1
wojtekmach
Hex Core Team
@sabondano I’m very much in favor of creating and keeping boundaries in my code. To respond to your particular example, I believe you’re referring to line: public_email = User.email(user, :public) in the controller [1]. If so, to be honest, I’m not too concerned about it because if you look into implementation of User.email/2 [2] you’d see it operates on user.emails field on the struct. I don’t want to draw the line what’s right and what’s wrong and it’s something I’m still developing an intuition on. However, what I’m sure is I’d be much more concerned if the controller would directly operate on Repo or Queries regarding the User schema.
To give more context (or to make excuses :)) we’ve introduced context modules several months before we’ve made the switch to Phoenix v1.3 structure and it’s still definitely rough around the edges. I think there’s still room for improvement and it’s something I want to pursue.
[1] hexpm/lib/hexpm/web/controllers/user_controller.ex at 0ce8169739d9baf061d6be5ba9e4940a7d0515b6 · hexpm/hexpm · GitHub
[2] hexpm/lib/hexpm/accounts/user.ex at 0ce8169739d9baf061d6be5ba9e4940a7d0515b6 · hexpm/hexpm · GitHub
2
MiLk
With the new configuration system:
on_init: {MyApp.Web.Endpoint, :load_from_system_env, []},
It seems we are forced to use IPv6 (phoenix/installer/templates/phx_web/endpoint.ex at 438b74255e7a4d68b4eaf1a295d0fcd201c71421 · phoenixframework/phoenix · GitHub).
If the old way to do config is deprecated (phoenix/lib/phoenix/endpoint/handler.ex at da9f7653b9daf29a4c415be52a19ee6f4473e083 · phoenixframework/phoenix · GitHub), how should I configure the port to work if I don’t have IPv6?
0
Gazler
Phoenix Core Team
You can remove :inet6 from the config. Change this:
{:ok, Keyword.put(config, :http, [:inet6, port: port])}
to this:
{:ok, Keyword.put(config, :http, [port: port])}
0
MiLk
Oh, I didn’t pay attention. I didn’t see it was actually a template used to generate a file in my project.
Thank you!
0