Upgrade to Phoenix 1.3

[jdesilvio]

Upgrade guide: https://gist.github.com/chrismccord/71ab10d433c98b714b75c886eff17357

[jdesilvio]

ndarilek commented on Mar 4, 2017

One point that was missed, which I noticed when generating a new 1.3 application:

• $ mv lib/my_app.ex lib/my_app/application.ex
• Change defmodule MyApp to defmodule MyApp.Application.
• Change the App in the mod parameter in mix.exs to MyApp.Application.

I didn't get that exactly right, but that's vaguely what I did. It isn't a breaking change, but if the goal is to make upgraded apps identical to newly-generated ones, that change should probably be documented.

[jdesilvio]

Optional change:

When migrating an existing app, you may want to rename MyApp.ModelCase to MyApp.DataCase, mv test/support/model_case.ex to test/support/data_case.ex, and update module references in existing model tests.

The new generators for creating a context and schema (formerly known as "model") will generate schema test cases with use MyApp.DataCase instead of MyApp.ModelCase, so you'll have to handle the missing module name somehow.

[jdesilvio]

https://www.phoenixdiff.org/ for changes in generated apps

[jdesilvio]

Created new issues for dealing with bigger upgrades that are not causing any immediate problems:

• https://github.com/jdesilvio/blaces/issues/13 Switch to schemas over models for data
• https://github.com/jdesilvio/blaces/issues/9 Upgrade to Guardian 1.x