Is your feature request related to a problem? Please describe.
When starting the project locally, dekick asks if it should re-seed the DB. It is however failing in our project due to existing relations. The seeders could clean-up before seeding, but that would be an overkill and a ton of work.
Describe the solution you'd like
The option to seed the database again should behave like dekick stop --remove as there is no point in keeping the previous DB. It's a simple solution that removes the burden of writing clean-up commands for each and every seeder.
Is your feature request related to a problem? Please describe.
When starting the project locally, dekick asks if it should re-seed the DB. It is however failing in our project due to existing relations. The seeders could clean-up before seeding, but that would be an overkill and a ton of work.
Describe the solution you'd like
The option to seed the database again should behave like
dekick stop --removeas there is no point in keeping the previous DB. It's a simple solution that removes the burden of writing clean-up commands for each and every seeder.