Posted on: Written by: K-Sato
⚠️ This article was posted over a year go. The information might be outdated. ⚠️

Table of Contents

About this post

This is a post for me to solidify the basic knowledge about Typescript I learnt from TypeScript Handbook.

Basic types

Tuple

Tuple types allow you to express an array with a fixed number of elements whose types are known, but need not be the same.

// Declare a tuple type
let x: [string, number]
// Initialize it
x = ['hello', 10] // OK
// Initialize it incorrectly
x = [10, 'hello'] // Error

Never

The never type represents the type of values that never occur. For instance, never is the return type for a function expression or an arrow function expression that always throws an exception or one that never returns.

// Function returning never must have unreachable end point
function error(message: string): never {
  throw new Error(message)
}

// Function returning never must have unreachable end point
function infiniteLoop(): never {
  while (true) {}
}

Object

object is a type that represents the non-primitive type, i.e. anything that is not number, string, boolean, bigint, symbol, null, or undefined.

declare function create(o: object | null): void

create({ prop: 0 }) // OK
create(null) // OK

create(42) // Error
create('string') // Error
create(false) // Error
create(undefined) // Error

Type assertions

Type assertions are a way to tell the compiler “trust me, I know what I’m doing.”.

It has no runtime impact, and is used purely by the compiler. TypeScript assumes that you, the programmer, have performed any special checks that you need.

let someValue: any = 'this is a string'

let strLength: number = (<string>someValue).length

And the other is the as-syntax:

let someValue: any = 'this is a string'

let strLength: number = (someValue as string).length

The two samples are equivalent. Using one over the other is mostly a choice of preference. However, when using TypeScript with JSX, only as-style assertions are allowed.

Interfaces

Readonly propertyies

Some properties should only be modifiable when an object is first created. You can specify this by putting readonly before the name of the property.

interface Point {
  readonly x: number
  readonly y: number
}

You can construct a Point by assigning an object literal. After the assignment, x and y can’t be changed.

let p1: Point = { x: 10, y: 20 }
p1.x = 5 // error!

TypeScript comes with a ReadonlyArray<T> type that is the same as Array<T> with all mutating methods removed.

let a: number[] = [1, 2, 3, 4]
let ro: ReadonlyArray<number> = a
ro[0] = 12 // error!
ro.push(5) // error!
ro.length = 100 // error!
a = ro // error!

On the last line of the snippet you can see that even assigning the entire ReadonlyArray back to a normal array is illegal.

You can still override it with a type assertion, though.

a = ro as number[]

readonly vs const

The easiest way to remember whether to use readonly or const is to ask whether you’re using it on a variable or a property.

Variables use const whereas properties use readonly.

Index signatures

Here we’re saying a SquareConfig can have any number of properties, and as long as they aren’t color or width, their types don’t matter.

interface SquareConfig {
  color?: string
  width?: number
  [propName: string]: any
}

Indexable Types

we can also describe types that we can “index into” like a[10], or ageMap["daniel"].

Indexable types have an index signature that describes the types we can use to index into the object, along with the corresponding return types when indexing.

interface StringArray {
  [index: number]: string
}

let myArray: StringArray
myArray = ['Bob', 'Fred']

let myStr: string = myArray[0]

Differences between interfaces and types in TypeScript

  • TypeScript Type declaration can introduce a name for any kind of type including primitive, union or intersection type. Interface declaration always introduced the named object type.
  • The syntax for Type can be written as ‘type ABC = {a: number; b: number;}’. The syntax for interface can be written as ‘interface ABC = {a: number; b: number;}’.
  • In TypeScript, type does not create a new name for instance. In TypeScript, an interface can create the new name that can be used everywhere.
  • Type does not have a functionality of extending. An interface can extend multiple interfaces and class as well.
  • Type is mainly used when a union or tuple type needs to be used. In typescript, sometimes developers cannot express some of the shapes with an interface.

TypeScript Type vs Interface

可変長引数

TS では可変長引数の部分の型は配列にします。次の例では...barnumber[]型が付いているため、2 番目以降の引数は全て数値でなければいけません。

const func = (foo: string, ...bar: number[]) => bar

func('foo')
func('bar', 1, 2, 3)
// エラー: Argument of type '"hey"' is not assignable to parameter of type 'number'.
func('baz', 'hey', 2, 3)

インデックスシグネチャ

オブジェクト型には実は今まで紹介した他にも記法があります。その一つがインデックスシグネチャです。

interface MyObj {
  [key: string]: number
}

const obj: MyObj = {}

const num: number = obj.foo
const num2: number = obj.bar

関数シグネチャ

実は、オブジェクト型の記法で関数型を表現する方法があります。

interface Func {
  (arg: number): void
}

const f: Func = (arg: number) => {
  console.log(arg)
}

Resources

About the author

I am a web-developer based somewhere on earth. I primarily code in TypeScript, Go and Ruby at work. React, RoR and Gin are my go-to Frameworks.