Migrations for EXTRA_MODEL_FIELDS need documentation

[jMyles]

The documentation (https://github.com/stephenmcd/mezzanine/blob/master/docs/model-customization.rst#field-injection-caveats) for this feature doesn't explicitly explain how to do this. Furthermore, since, starting with Django 1.7, migrations need to live in the app which contains the model in question, the process is quite different and non-trivial.

Take a look at this writeup on the process in 1.7 - if there are no objections, I can modify this to fit into the docs.

[stephenmcd]

I'd be happy to include a very brief description - no more than a paragraph or two. Really don't want to litter the docs with discussions of workarounds for a misfeature like this. Eventually I hope it can be removed with use of swappable models.

[jMyles]

Ahh, so you regard EXTRA_MODEL_FIELDS as a "misfeature?" Is there a place
I can read the discussion that led to this state?

As I said in my blog post, I will continue to look into swappable models.

On Sun, Nov 9, 2014 at 2:32 AM, Stephen McDonald notifications@github.com
wrote:

I'd be happy to include a very brief description - no more than a
paragraph or two. Really don't want to litter the docs with discussions of
workarounds for a misfeature like this. Eventually I hope it can be removed
with use of swappable models.

—
Reply to this email directly or view it on GitHub
#1150 (comment)
.

[AlexHill]

Hi Steve,

I'm interested to hear what you'd like swappable models in Mezzanine to
look like. I think it's a great idea, particularly for Cartridge.

Alex

On Sunday, 9 November 2014, Stephen McDonald notifications@github.com
wrote:

I'd be happy to include a very brief description - no more than a
paragraph or two. Really don't want to litter the docs with discussions of
workarounds for a misfeature like this. Eventually I hope it can be removed
with use of swappable models.

—
Reply to this email directly or view it on GitHub
#1150 (comment)
.

[stephenmcd]

I've created a new issue #1160 with initial thoughts.