diff options
| author | dubiousjim <dubiousjim@gmail.com> | 2020-03-07 22:29:12 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-07 22:29:12 -0500 |
| commit | 0dd131d4a512e8e8370b571d6801eabb4cb30e58 (patch) | |
| tree | 24471f2f1c33cd6516b0cd1bc8efeb07576b83ad /cli/js/copy_file_test.ts | |
| parent | 8d1ba3552fbbcae9284fdab63cc6613045684d01 (diff) | |
Rename perm to mode (#4276)
There's a lot of variation in doc comments and internal code about
whether chmod/0o777-style permissions are called `mode` or `perm`. (For
example, mkdir and writeFile choose differently.)
Had proposed earlier to go consistently with `perm`, but on balance devs
prefer to go with `mode`.
Diffstat (limited to 'cli/js/copy_file_test.ts')
| -rw-r--r-- | cli/js/copy_file_test.ts | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/cli/js/copy_file_test.ts b/cli/js/copy_file_test.ts index 39e1c0256..986bab53b 100644 --- a/cli/js/copy_file_test.ts +++ b/cli/js/copy_file_test.ts @@ -10,7 +10,7 @@ function readFileString(filename: string): string { function writeFileString(filename: string, s: string): void { const enc = new TextEncoder(); const data = enc.encode(s); - Deno.writeFileSync(filename, data, { perm: 0o666 }); + Deno.writeFileSync(filename, data, { mode: 0o666 }); } function assertSameContent(filename1: string, filename2: string): void { |