Description
Description
Remove templates from the core and move them to plugins instead. This should enable more flexibility in creating own templates.
Implementation Details
The core will provide the plugin with the passed arguments configured and requested by the plugin and takes care of actually writing the migration to disk. A plugin may only provide 2 files in case of non db-migrate related migration schemas (like SQL-files) which need to be passed properly defined and separated into up and down categories. Normal migrations just simply pass their template to db-migrate and specify optionally a different file ending. If additionally any more files that are not migrations themselves, i.e. configuration files, need to be written the core will provide the plugin an api for that as well. The core will only allow to write files within the migration folder, in any other case the plugin needs to take care of this itself.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.