Typescript declaring null

interface Employee1 {
    name: string;
    salary: number;
}

var a: Employee1 = { name: 'Bob', salary: 40000 }; // OK
var b: Employee1 = { name: 'Bob' }; // Not OK, you must have 'salary'
var c: Employee1 = { name: 'Bob', salary: undefined }; // OK
var d: Employee1 = { name: null, salary: undefined }; // OK

// OK
class SomeEmployeeA implements Employee1 {
    public name = 'Bob';
    public salary = 40000;
}

// Not OK: Must have 'salary'
class SomeEmployeeB implements Employee1 {
    public name: string;
}

-1

Source: stackoverflow.com

Similar codes

1 vote178 views1 answer
Dispatcher servlet as its web application context
TypeScript
0 vote193 views1 answer
Material ui iccons
TypeScript
0 vote236 views1 answer
Linux copy all directory contents to another directory
TypeScript
0 vote147 views1 answer
Allow specific string in type
TypeScript
0 vote195 views1 answer
Angular build failed to load router-outlet
TypeScript
0 vote188 views1 answer
Ipywidgets hide widget
TypeScript
2 votes187 views1 answer
Socketi io client disconnect
TypeScript
0 vote194 views1 answer
Array<Type> VS Type[] in Typescript
TypeScript
0 vote223 views1 answer
Dictionary comprehension using while copying elements from another dictionary in python
TypeScript
1 vote207 views2 answers
No type arguments expected for interface Callback
TypeScript