Loading and running the migration directly from the package does not allow customisation of the database table to fit the application. Also, it does not allow the user to use the filename's timestamp prefix to determine when the migration is run in relation to other migrations.
If the migration is published, the user can modify both the filename's timestamp to control when it is run and the column types to suit the needs of the app.
E.g. changing ->morphs() to ->uuidMorphs for users using uuid primary key fields.
Resolves #15
Loading and running the migration directly from the package does not allow customisation of the database table to fit the application. Also, it does not allow the user to use the filename's timestamp prefix to determine when the migration is run in relation to other migrations.
If the migration is published, the user can modify both the filename's timestamp to control when it is run and the column types to suit the needs of the app.
E.g. changing ->morphs() to ->uuidMorphs for users using uuid primary key fields.