【问题标题】:Typescript: Object is possibly 'undefined'打字稿:对象可能是“未定义”
【发布时间】:2019-07-30 18:59:57
【问题描述】:

我很好奇为什么我会在下面收到 Typescript 警告。

此行出现错误:a[k].toString().toLowerCase()

但是我检查了if (a && a[k]),它应该确保在下一行中,aa[k] 不能未定义?

// Return coins that match text search by currency symbol or name.
export const findAsset = (txt: string, assets: IAsset[] | null[]) => {
  // assets will exist here...
  if (assets) {
    // Typescript error here...
    const checkText = (k: string, a: IAsset | null) => {
      if (a && a[k]) {
        return (textMatch(txt.toLowerCase(), a[k].toString().toLowerCase()) ? a : null);
      }
    }
    const curriedCheckText = R.curry(checkText);
    const byName = R.map(curriedCheckText('name'), assets);
    const bySymbol = R.map(curriedCheckText('currency'), assets);
    const matchNames = R.reject(R.isNil, byName);
    const matchSymbols = R.reject(R.isNil, bySymbol);
    const combinedSearch = (matchNames.concat(matchSymbols));
    return R.uniq(combinedSearch);
  }
  else {
    return [];
  }
};

这是IAsset界面的形状

export interface IAsset {
  [key: string]: string | number | undefined | boolean;
  availableSupply?: string;
  currency: string;
  exchange: string;
  exchange_base?: string;
  marketCap: number;
  name: string;
  percentage?: number;
  price: number;
  position?: number;
  value?: number;
  inWatchlist?: boolean;
}

tsconfig

{
  "compilerOptions": {
    /* Basic Options */
    "target": "es5" /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017','ES2018' or 'ESNEXT'. */,
    "module": "commonjs" /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', or 'ESNext'. */,
    "lib": [
      "dom",
      "es2015",
      "es2016",
      "es2017",
    ], /* Specify library files to be included in the compilation. */,
    "allowJs": true,                       /* Allow javascript files to be compiled. */
    "checkJs": true,                       /* Report errors in .js files. */
    "jsx": "react",                     /* Specify JSX code generation: 'preserve', 'react-native', or 'react'. */
    "declaration": true,                   /* Generates corresponding '.d.ts' file. */
    "declarationMap": true,                /* Generates a sourcemap for each corresponding '.d.ts' file. */
    "sourceMap": true,                     /* Generates corresponding '.map' file. */
    // "outFile": "./",                       /* Concatenate and emit output to single file. */
    // "outDir": "./",                        /* Redirect output structure to the directory. */
    // "rootDir": "./",                       /* Specify the root directory of input files. Use to control the output directory structure with --outDir. */
    // "composite": true,                     /* Enable project compilation */
    // "removeComments": true,                /* Do not emit comments to output. */
    "noEmit": true,                        /* Do not emit outputs. */
    // "importHelpers": true,                 /* Import emit helpers from 'tslib'. */
    "resolveJsonModule": true,
    "downlevelIteration": true,            /* Provide full support for iterables in 'for-of', spread, and destructuring when targeting 'ES5' or 'ES3'. */
    // "isolatedModules": true,               /* Transpile each file as a separate module (similar to 'ts.transpileModule'). */

    /* Strict Type-Checking Options */
    "strict": true /* Enable all strict type-checking options. */,
    "noImplicitAny": true /* Raise error on expressions and declarations with an implied 'any' type. */,
    "strictNullChecks": true /* Enable strict null checks. */,
    "strictFunctionTypes": true /* Enable strict checking of function types. */,
    "strictBindCallApply": true /* Enable strict 'bind', 'call', and 'apply' methods on functions. */,
    "strictPropertyInitialization": true /* Enable strict checking of property initialization in classes. */,
    "noImplicitThis": true /* Raise error on 'this' expressions with an implied 'any' type. */,
    "alwaysStrict": true /* Parse in strict mode and emit "use strict" for each source file. */,

    /* Additional Checks */
    // "noUnusedLocals": true,                /* Report errors on unused locals. */
    // "noUnusedParameters": true,            /* Report errors on unused parameters. */
    // "noImplicitReturns": true,             /* Report error when not all code paths in function return a value. */
    // "noFallthroughCasesInSwitch": true,    /* Report errors for fallthrough cases in switch statement. */

    /* Module Resolution Options */
    // "moduleResolution": "node",            /* Specify module resolution strategy: 'node' (Node.js) or 'classic' (TypeScript pre-1.6). */
    // "baseUrl": "./",                       /* Base directory to resolve non-absolute module names. */
    // "paths": {},                           /* A series of entries which re-map imports to lookup locations relative to the 'baseUrl'. */
    // "rootDirs": [],                        /* List of root folders whose combined content represents the structure of the project at runtime. */
    // "typeRoots": [],                       /* List of folders to include type definitions from. */
    // "types": [],                           /* Type declaration files to be included in compilation. */
    // "allowSyntheticDefaultImports": true,  /* Allow default imports from modules with no default export. This does not affect code emit, just typechecking. */
    "esModuleInterop": true, /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
    // "preserveSymlinks": true,              /* Do not resolve the real path of symlinks. */

    /* Source Map Options */
    // "sourceRoot": "",                      /* Specify the location where debugger should locate TypeScript files instead of source locations. */
    // "mapRoot": "",                         /* Specify the location where debugger should locate map files instead of generated locations. */
    // "inlineSourceMap": true,               /* Emit a single file with source maps instead of having a separate file. */
    // "inlineSources": true,                 /* Emit the source alongside the sourcemaps within a single file; requires '--inlineSourceMap' or '--sourceMap' to be set. */

    /* Experimental Options */
    "experimentalDecorators": true,        /* Enables experimental support for ES7 decorators. */
    // "emitDecoratorMetadata": true,         /* Enables experimental support for emitting type metadata for decorators. */
  },
  "include": [
    "components/**/*",
    "pages/**/*",
  ],
  "exclude": [
    "node_modules",
    "styles",
    "_document.tsx"
  ]
}

【问题讨论】:

  • 当我复制到我的编辑器时,我没有收到任何错误。你的tsconfig.json 有问题吗?
  • 你能分享你的tsconfig.json文件吗
  • @GetOffMyLawn Daniel 刚刚发布了!
  • 相关问题:github.com/Microsoft/TypeScript/issues/28081 和/或github.com/Microsoft/TypeScript/issues/10530。最简单的类型安全解决方法是将a[k] 分配给一个新变量,然后对其进行检查。最简单的非类型安全解决方法是在if 语句的真实块中使用非空断言a[k]!
  • 由于[key: string] 可以有undefined 值,因此您不能在其上使用toString(a[k]||'').toString() 工作...

标签: javascript typescript


【解决方案1】:

在 Angular 中,我使用了 ngIF 并为我解决了问题。

<div *ngIf="user" class="row">
<div class="input-field col s6">
  <input
    [(ngModel)]="user.firstName"
    placeholder="Placeholder"
    id="first_name"
    type="text"
    class="validate"
  />
  <label for="first_name">First Name</label>
</div>

【讨论】:

    【解决方案2】:

    抑制 VUE 模板中的错误

    如果您了解错误并想知道如何在 VUE 模板中处理它:只需在父元素中放置一个条件

    <div v-if="user">
       <p>Hallo {{user.firstName}}</p>
    </div>
    

    【讨论】:

      【解决方案3】:

      我可以想到两种方法来消除错误。

      我能想到的第一种方法是使用带有|| 运算符的后备,这会变成

      a[k].toString().toLowerCase()
      

      进入这个,所以如果值是假的,那么使用一个空字符串。

      (a[k] || '').toString().toLowerCase()
      // Or with optional chaining
      a[k]?.toString().toLowerCase() || ''
      

      另一种方法是将值保存到变量并检查新变量。然后这就是

      if (a && a[k]) {
        return textMatch(txt.toLowerCase(), a[k].toString().toLowerCase()) ? a : null;
      }
      

      变成这样:

      let v = a ? a[k] : null
      if (v) {
        return textMatch(txt.toLowerCase(), v.toString().toLowerCase()) ? a : null;
      }
      

      【讨论】:

        【解决方案4】:

        不确定这是否 100% 适用于您的问题,自从 TypeScript 3.7 发布以来,optional chaining? 运算符)的使用绝对是另一个需要探索的相关解决方案。你可以安装最新的稳定版 TypeScript:

        npm install typescript
        

        因此,checkText 可以通过使用可选的链接运算符来简化。

        const checkText = (k: string, a: IAsset | null) => {
          return (textMatch(txt.toLowerCase(), a?.[k].toString().toLowerCase()) ? a : null);
        }
        

        【讨论】:

          【解决方案5】:

          Typescript 不会保留有关特定数组索引处的值的类型信息。例如,这是一个错误:

          function test(a: (number | string)[]) {
              if (typeof a[3] === "number") {
                  const num: number = a[3];
              }
          }
          

          要获得可以包含类型信息的内容,您可以将a[k] 放入其他变量中,如下所示:

          const checkText = (k: string, a: IAsset | null) => {
          if (a) {
            const atK = a[k];
            if (atK) {
              return (textMatch(txt.toLowerCase(), atK.toString().toLowerCase()) ? a : null);
            }
          }
          

          或者你可以转换它,因为你比类型系统更了解类型:

          const checkText = (k: string, a: IAsset | null) => {
            if (a && a[k]) {
              return (textMatch(txt.toLowerCase(), (a[k] as string | number | true).toString().toLowerCase()) ? a : null);
            }
          }
          

          或者您可以通过使用字符串插值来避免担心未定义:

          const checkText = (k: string, a: IAsset | null) => {
            if (a && a[k]) {
              return (textMatch(txt.toLowerCase(), `${a[k]}`.toLowerCase()) ? a : null);
            }
          }
          

          理想情况下,类型系统会处理这些事情,但我确信这种类型信息通常不可用是有原因的。

          【讨论】:

            猜你喜欢
            • 2019-09-15
            • 1970-01-01
            • 2021-01-19
            • 2019-12-24
            • 1970-01-01
            • 2021-08-24
            • 2021-08-06
            • 2021-12-21
            • 2021-08-08
            相关资源
            最近更新 更多