Add the ability to pass in a folder containing migration scripts.

[joe-allen-89]

Currently the only way to include migration scripts is within a plugin, it would be useful, especially in the authoring tool, to be able to have a seperate folder containing multiple scripts, for example updating the start controller on course import.

[oliverfoster]

Script paths are passed in from grunt. This library doesn't find the scripts itself.
Could you be more specific about the start controller migration scripts please? Why could they not live in core where the start controller lives?

[joe-allen-89]

Script paths are passed in from grunt. This library doesn't find the scripts itself. Could you be more specific about the start controller migration scripts please? Why could they not live in core where the start controller lives?

Realised I raised it in the wrong place was just about to transfer.

When importing a course into the authoring tool the ids are reset meaning that the id listed in the start controller isn't linking to anything, with a migration script we can find the item the start controller is targetting and give it a friendlyid as well as updating the start controller. This was probably a bad example as it could live in core, albeit only being an authoring tool issue.

A better example would be Tom had made some migration scripts for the authoring tool (https://github.com/adapt-security/adapt-authoring-adaptframework/tree/master/lib/migrations), the ability to set a custom folder would allow us to update these to work with adapt-migrations and have a standaridised approach.

[oliverfoster]

Yup, passing a custom folder through the grunt options would be cool --customscriptsdir=