You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working on multiple dev branches, sometimes I end up with database with broken migrations. There's README entry for situations like this, but it might be a good idea to add cleanup command to Makefile
due to the destructive nature of this command, the user should be presented with a warning and confirmation (with default set to abort the operation)
Extra points
It seems to be a common issue for casual/new platform users - sometimes, database just doesn't populate after some experiments. If the makefile command bootstrap could inform users about possible causes, it would help a lot.
Example:
run bootstrap command
migration command fails
user is presented with the message explaining what could be a cause and suggesting cleanup as one of the solutions
The text was updated successfully, but these errors were encountered:
The problem I would like to solve:
When working on multiple dev branches, sometimes I end up with database with broken migrations. There's README entry for situations like this, but it might be a good idea to add
cleanup
command to MakefileSolution
cleanup
command (https://github.com/saleor/saleor-platform#issues-with-migrations-after-changing-the-versions---resetting-the-database)Extra points
It seems to be a common issue for casual/new platform users - sometimes, database just doesn't populate after some experiments. If the makefile command
bootstrap
could inform users about possible causes, it would help a lot.Example:
bootstrap
commandThe text was updated successfully, but these errors were encountered: