bitburner-src/src/Script/isScriptFilename.ts

export const validScriptExtensions: Array<string> = [`.js`, `.script`, `.ns`];

export function isScriptFilename(f: string): boolean {
  return validScriptExtensions.some((ext) => f.endsWith(ext));
}
fix(commands): error feedback, wording consistency Found most (hopefully all) places where the error message wording incorrectly was shown to the tune of 'no script exists', where it should have been showing to the effect of 'script is not running'. Also cleaned up some of the consistency in the wording and added a 'helper' export for knowing valid script extensions used in validation of 'isScriptFilename', so we can have consistent error messaging. Resolves danielyxie/bitburner#1966 2021-12-19 04:10:43 +01:00			export const validScriptExtensions: Array<string> = [`.js`, `.script`, `.ns`];

all the lints 2021-05-01 09:17:31 +02:00			`export function isScriptFilename(f: string): boolean {`
fix(commands): error feedback, wording consistency Found most (hopefully all) places where the error message wording incorrectly was shown to the tune of 'no script exists', where it should have been showing to the effect of 'script is not running'. Also cleaned up some of the consistency in the wording and added a 'helper' export for knowing valid script extensions used in validation of 'isScriptFilename', so we can have consistent error messaging. Resolves danielyxie/bitburner#1966 2021-12-19 04:10:43 +01:00			`return validScriptExtensions.some((ext) => f.endsWith(ext));`
Refactored Server/Script/Files code to TypeScript 2019-03-05 02:40:28 +01:00			`}`