When Phoenix 1.3 and Contexts were introduced, I got more excited because I really think this is a good idea. So I began to try to learn and understand these new concepts. However, the official guides and the Programming Phoenix book haven’t been updated yet for Phoenix 1.3.
I’d like to add that this has been true for me as well. As an beginner-to-intermediate-level coder, I want to know that I’m learning things “correctly” - as in best practices - as opposed to piecing things together and somewhat feeling around in the dark, which can be disheartening. (The fact that generators aren’t necessarily best practice, as most would assume, adds to this)
When it comes to Contexts, an example of this is when in this thread Jose wonders:
I wonder how much cheating would it be to do something like mix phoenix.gen.html Posts Post “posts” … for those cases.
I wondered the same on Slack about a month ago, and Chris responded saying that this (Context and Schema having the same name) is likely not right - and there’s probably a better context name out there for me to find.
In my dream scenario, the core team would build out their own complex (not just Blog.example) example app with multiple contexts, shared schemas, etc. To get a sense of what you think about naming standards, associations, etc. Even if it comes with a disclaimer or caveat about how every app is different, this would help give newbies a baseline/starting point.
In my super dream scenario, Phoenix would adopt an approach similar to Ember’s - where guides and features are released in tandem, and there are periodic updates on what the core team is thinking and working on: Ember.js Blog
Thanks so much for the work you do @chrismccord, @josevalim, and team!
