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/write_file.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/write_file.ts')
-rw-r--r-- | cli/js/write_file.ts | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/cli/js/write_file.ts b/cli/js/write_file.ts index 3986eed78..d57274228 100644 --- a/cli/js/write_file.ts +++ b/cli/js/write_file.ts @@ -13,7 +13,7 @@ export interface WriteFileOptions { * exist at the specified path (defaults to `true`). */ create?: boolean; /** Permissions always applied to file. */ - perm?: number; + mode?: number; } /** Synchronously write data to the given path, by default creating a new @@ -41,8 +41,8 @@ export function writeFileSync( const openMode = !!options.append ? "a" : "w"; const file = openSync(path, openMode); - if (options.perm !== undefined && options.perm !== null) { - chmodSync(path, options.perm); + if (options.mode !== undefined && options.mode !== null) { + chmodSync(path, options.mode); } writeAllSync(file, data); @@ -74,8 +74,8 @@ export async function writeFile( const openMode = !!options.append ? "a" : "w"; const file = await open(path, openMode); - if (options.perm !== undefined && options.perm !== null) { - await chmod(path, options.perm); + if (options.mode !== undefined && options.mode !== null) { + await chmod(path, options.mode); } await writeAll(file, data); |