|
1 | | - |
2 | 1 | /** |
3 | | - * Our first transition is actually the removal of globals and |
4 | | - * introducing the setup routine. |
5 | | - * Thus the body of this transition is just an empty function, but displays |
6 | | - * as all transitions an explanation to the user. |
7 | | - */ |
| 2 | + * Our first transition is actually the removal of globals and |
| 3 | + * introducing the setup routine. |
| 4 | + * Thus the body of this transition is just an empty function, but displays |
| 5 | + * as all transitions an explanation to the user. |
| 6 | + */ |
8 | 7 | module.exports = { |
9 | | - |
10 | | - transition: function () { |
11 | | - |
12 | | - }, |
| 8 | + transition: function () {}, |
13 | 9 |
|
14 | 10 | message: function () { |
15 | | - console.log('Congratulations!\n\n' + |
16 | | - 'You just migrated from protocol 0 to 1!\n' + |
17 | | - 'What does that mean for you?\n' + |
18 | | - 'Quite simple, from 0 to 1 we introduced the setup function and we' + |
19 | | - 'deprecated some globals, like async or dbm. What this transition does is' + |
20 | | - ' grabbing your migrations, replacing the async and dbm definitions and ' + |
21 | | - 'inserting the setup body if not present.\n' + |
22 | | - 'It might be possible, that you still run into errors, for example if ' + |
23 | | - 'you already have had a setup body, it wont be replaced and you might ' + |
24 | | - 'be missing the default routine of the setup, which provides for example ' + |
25 | | - 'the dataTypes to your migration.\n\n' + |
26 | | - 'What do I need to do now?\n' + |
27 | | - 'Try to rexecute all of your migrations and watch if you run into any ' + |
28 | | - 'Errors, if you encounter any, you need to manually fix those ' + |
29 | | - 'problems. But don\'t worry, this protocol transitions happen very ' + |
30 | | - 'rarely!\n' |
| 11 | + console.log( |
| 12 | + 'Congratulations!\n\n' + |
| 13 | + 'You just migrated from protocol 0 to 1!\n' + |
| 14 | + 'What does that mean for you?\n' + |
| 15 | + 'Quite simple, from 0 to 1 we introduced the setup function and we ' + |
| 16 | + 'deprecated some globals, like async or dbm. What this transition does is' + |
| 17 | + ' grabbing your migrations, replacing the async and dbm definitions and ' + |
| 18 | + 'inserting the setup body if not present.\n' + |
| 19 | + 'It might be possible, that you still run into errors, for example if ' + |
| 20 | + 'you already have had a setup body, it wont be replaced and you might ' + |
| 21 | + 'be missing the default routine of the setup, which provides for example ' + |
| 22 | + 'the dataTypes to your migration.\n\n' + |
| 23 | + 'What do I need to do now?\n' + |
| 24 | + 'Try to rexecute all of your migrations and watch if you run into any ' + |
| 25 | + 'Errors, if you encounter any, you need to manually fix those ' + |
| 26 | + "problems. But don't worry, this protocol transitions happen very " + |
| 27 | + 'rarely!\n' |
31 | 28 | ); |
32 | 29 | } |
33 | 30 | }; |
0 commit comments