New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor Mapstories + Storyframes + Storypins Apps #1189
Conversation
…ternal naming. Migration added to change model names in database, tests passing.
…model instead of removing it.
…the ones in the apps directory.
…factor-mapstories-app
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these migrations.RenameModel()
s sufficient? They handle renaming the tables and migrating the data?
Sorry getting staging back up is taking a while. I'm getting distracted by other things. But I'd like to run it on staging before we do it on prod.
Yes the migrations should do what we need. It'll rename the database tables without deleting the data. I tested it locally, but I would agree testing it on staging (after staging has some stories with layers, pins and frames) makes sense. |
This PR refactors the naming used in the mapstories, storyframes and storypins apps. They were previously called boxes and annotations which did not line up with what we called these features. This must be merged at the same time as this MapLoom PR. MapStory/MapLoom#42