Migrations based on environment about loopback-component-migrate HOT 2 OPEN

@antonsamper I'm curious, why would you ever want to do this? I worked with Rails for a while and all migrations ran on all environments.

from loopback-component-migrate.

@sundeepgupta In general, I agree that migrations should run on all environments but it does depend on what the migration is doing. In my case I was using them to add data to the database. At the time, i was trying to setup up a fully functional dev environment (including dummy data) so that coworkers could get the app running without having to manually add anything. However, as this was dummy data, i didn't want it in production.

I know i could add environment checks in the migrations but i thought it could be quite nice to take the existing concept of appending the environment name to the filename.

from loopback-component-migrate.