@@ -29,13 +29,18 @@ checking, which makes this so important but difficult. The `err2` package writes
29
29
problems to ` stderr ` because it cannot panic in middle of the panicking. Note.
30
30
This is only a legacy code problem. We are migration as you see :-)
31
31
32
+ #### Manual v0.9.40 Migration With Location List (nvim/vim)
33
+
32
34
Follow these steps check do you have migration needs for v0.9.40:
33
35
1 . [ Set up Migration Environment] ( #set-up-migration-environment )
34
- 1 . Execute following command:
36
+ 1 . Execute following command in your repo's root directory :
35
37
``` shell
36
- migr-name.sh todo_handle_func todo_catch_func
38
+ migr-name.sh -ndv todo_handle_func todo_catch_func
37
39
```
38
40
41
+ * Tip. If your repo is large and you have many migration changes see the next
42
+ [ semi-automatic guide] ( #semi-automatic-v0.9.40-migration ) .*
43
+
39
44
* Tip. You can execute that command from e.g. nvim/vim and you get your fix list.*
40
45
``` shell
41
46
migr-name.sh todo_handle_func todo_catch_func > todo_list
@@ -46,10 +51,20 @@ nvim -q todo_list
46
51
nvim -q <( migr-name.sh todo_handle_func todo_catch_func)
47
52
```
48
53
49
- ** Note. We are still in middle to process check if we can make this migration
50
- automatic, at least semi-automatic. Probably we cannot do the same as with
51
- others because the error value setting isn't closure anymore where we can refer
52
- the ` err ` return variable directly.**
54
+ #### Semi-Automatic v0.9.40 Migration
55
+
56
+ Follow these steps:
57
+ 1 . [ Set up Migration Environment] ( #set-up-migration-environment )
58
+ 1 . Make sure that you haven't uncommitted changes in your repo and that you are
59
+ in the branch where you want to make the changes.
60
+ 1 . Execute following command in your repo's root directory:
61
+ ``` shell
62
+ migr-name.sh -ndv repl_handle_func repl_catch_func
63
+ ```
64
+ 1 . Then continue with ` build ` , ` test ` , ` lint ` , etc. ** And don't stop yet.**
65
+ 1 . Use ` git diff ` or similar to skimming that all changes seem to be OK. Here
66
+ you have an opportunity to start use new features of ` err2 ` like logging.
67
+ 1 . You are ready to commit changes.
53
68
54
69
### ` assert.SetDefaultAsserter ` -> ` assert.SetDefault ` and others in v0.9.1
55
70
0 commit comments