makemigrations fails to recognize new models in arches applications

[chiatt]

When a user creates a new Arches App, the app contains a models directory rather than a models.py file. If an app developer creates models within the models directory and then runs makemigrations, django will not find the models and no migration will be created. If a models.py file is added outside of the models directory, and the user runs makemigrations, django will still fail to find the new models. Using a models.py file and removing the models directory fixes this issue.

New apps should probably not add a models directory, but just a models.py file. This would also be consistent with the default structure of a new Django app.

[jacobtylerwalls]

New apps should probably not add a models directory, but just a models.py file. This would also be consistent with the default structure of a new Django app.

👍

Apps that anticipate having a large number of models can use the folder structure if they remember to import the models in __init__.py or add a wildcard import there.

[chiatt]

Good point. That should probably be added to the docs.