You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[move-cli] Rename binary and reorganize project tree
The move-cli binary is now just named move. The crate did not change names,
only the binary it produces.
The following directories were renamed:
move_src -> src/modules and src/scripts
move_data -> storage
move_build_output -> build
Closes: diem#6622
@@ -30,11 +32,11 @@ Place this in a file named `script.move` and try
30
32
31
33
The `--signers 0xf` part indicates which account address(es) have signed off on the script. Omitting `--signers` or passing multiple signers to this single-`signer` script will trigger a type error.
32
34
33
-
## Adding new modules via `move_src`
35
+
## Adding new modules via `src`
34
36
35
-
By default, the CLI compiles and includes all files from the Move standard library and Libra Framework. New modules can be added to the `move_src` directory (or a directory of your choosing specified via `--move-src`. The `move run` command will compile and publish each module source file in this directory before running the given script.
37
+
By default, the CLI compiles and includes all files from the Move standard library and Libra Framework. New modules can be added to the `src` directory (or a directory of your choosing specified via `--source-dir`. The `move run` command will compile and publish each module source file in this directory before running the given script.
36
38
37
-
Try saving this code in `move_src/Test.move`:
39
+
Try saving this code in `src/modules/Test.move`:
38
40
39
41
```
40
42
module Test {
@@ -64,25 +66,25 @@ Compiling 1 user module(s)
64
66
Discarding changes; re-run with --commit if you would like to keep them.
65
67
```
66
68
67
-
The CLI has successfully compiled the module, but by default it chooses not to publish the module bytecode under `move_data`. Re-running the command with `--commit` (`-c` for short) will produce
69
+
The CLI has successfully compiled the module, but by default it chooses not to publish the module bytecode under `storage`. Re-running the command with `--commit` (`-c` for short) will produce
68
70
69
71
```
70
72
λ move compile -c
71
73
Compiling 1 user module(s)
72
74
Committed changes.
73
75
```
74
76
75
-
If we take a look under `move_data`, we will now see the published bytecodes for our test module:
77
+
If we take a look under `storage`, we will now see the published bytecodes for our test module:
76
78
77
79
```
78
-
λ ls move_data/0x00000000000000000000000000000002/modules
80
+
λ ls storage/0x00000000000000000000000000000002/modules
79
81
Test
80
82
```
81
83
82
84
We can also inspect the compiled bytecode using `move view`:
0 commit comments