[TypeScript] Use the TypeScript "unknown" type to avoid runtime errors

The "any" type can be very useful, especially when adding types to an existing JavaScript codebase, but it can also lead to lots of runtime errors, as it provides no type-checking. The "unknown" type on the other hand, restricts developer from calling anything on it or assigning to any other type. The only way to use "unknown" variables is to apply logic flow type narrowing or casting, as that's the only way TypeScript can trust that it's dealing with a correct type. The "unknown" type is useful when building services or APIs that can return data of an unknown shape, so we might want to stop other developers from using it in potentially dangerous ways until it's been narrowed down to a specific type.

"any" type can pass in the compile phases without any problem, but will throw error in runtime.

We can use new type: 'unknown'.

For exmaple, we have code:

interface IComment {

    date: Date;

    message: string;

}

interface IDataService {

    getData(): unknown;

}

let service: IDataService;

const response = service.getData();

You cannot directly use 'unknown' type, we have to tell Typescipt what type it is:

if(typeof response === 'string') {

    console.log(response.toUpperCase());

} else if(isComment(response)){

    response.date;

}

function isComment(type: any): type is IComment {

    return (<IComment>type).message !== undefined && (<IComment>type).date !== undefined;

}

巴特西

[TypeScript] Use the TypeScript "unknown" type to avoid runtime errors

最新文章

热门文章