ConstructorParameters type in Typescript - Time & Space Complexity
We want to understand how the time needed to get constructor parameters changes as the class constructor changes.
How does the work grow when the constructor has more or fewer parameters?
Analyze the time complexity of this TypeScript code using ConstructorParameters.
class Person {
constructor(public name: string, public age: number) {}
}
type Params = ConstructorParameters;
function createInstance(args: Params) {
return new Person(...args);
}
This code extracts the constructor parameter types of Person and uses them to create a new instance.
Look for loops or repeated steps in the code.
- Primary operation: Spreading the constructor arguments with
...args. - How many times: Once per call to
createInstance.
The time to create an instance grows with the number of constructor parameters.
| Input Size (number of parameters) | Approx. Operations |
|---|---|
| 2 | 2 operations to spread arguments |
| 5 | 5 operations to spread arguments |
| 10 | 10 operations to spread arguments |
Pattern observation: The work grows linearly as the number of constructor parameters increases.
Time Complexity: O(n)
This means the time to handle constructor parameters grows directly with how many parameters there are.
[X] Wrong: "Using ConstructorParameters is instant and does not depend on the number of parameters."
[OK] Correct: Each parameter must be handled when spreading, so more parameters mean more work.
Understanding how TypeScript utility types relate to runtime behavior helps you explain code efficiency clearly and confidently.
What if the constructor had optional parameters? How would that affect the time complexity?
Practice
What does the ConstructorParameters type utility do in TypeScript?
Solution
Step 1: Understand the purpose of ConstructorParameters
TheConstructorParametersutility extracts the types of the parameters used in a class constructor and returns them as a tuple type.Step 2: Compare with other options
Options B, C, and D describe different behaviors thatConstructorParametersdoes not perform.Final Answer:
Extracts the types of a class constructor's parameters as a tuple -> Option AQuick Check:
ConstructorParameters = tuple of constructor args [OK]
- Confusing ConstructorParameters with ReturnType
- Thinking it creates a new class
- Assuming it returns a union type
Which of the following is the correct syntax to get the constructor parameter types of a class MyClass using ConstructorParameters?
class MyClass { constructor(name: string, age: number) {} }Solution
Step 1: Identify the correct type argument for ConstructorParameters
The argument must be a constructor function type, which istypeof MyClass(the class constructor type), not the instance type.Step 2: Check each option
type Params = ConstructorParameters<MyClass>; uses the instance type, which is incorrect. type Params = ConstructorParameters; uses a non-existent property. type Params = ConstructorParameters; uses invalid syntax. Only type Params = ConstructorParameters; correctly usestypeof MyClass.Final Answer:
type Params = ConstructorParameters<typeof MyClass>; -> Option BQuick Check:
Use typeof ClassName with ConstructorParameters [OK]
- Passing instance type instead of constructor type
- Using invalid syntax like new expressions
- Trying to access constructor property
What is the output type of the following code?
class Person {
constructor(public name: string, public age: number) {}
}
type Params = ConstructorParameters<typeof Person>;Solution
Step 1: Analyze the constructor parameters
The constructor takes two parameters:nameof typestringandageof typenumber.Step 2: Understand ConstructorParameters output
ConstructorParameters<typeof Person>returns a tuple of the parameter types:[string, number].Final Answer:
[string, number] -> Option CQuick Check:
ConstructorParameters returns tuple of constructor arg types [OK]
- Expecting parameter names in the tuple
- Confusing parameter types with instance properties
- Thinking it returns an error
Identify the error in this code snippet:
class Car {
constructor(make: string, year: number) {}
}
type Params = ConstructorParameters<Car>;Solution
Step 1: Check the argument passed to ConstructorParameters
The argument must be the constructor function type, which istypeof Car, not the instance typeCar.Step 2: Identify the error
UsingCardirectly causes a type error because it is the instance type, not the constructor type.Final Answer:
Car is an instance type, should use typeof Car -> Option AQuick Check:
Use typeof ClassName with ConstructorParameters [OK]
- Passing instance type instead of constructor type
- Assuming ConstructorParameters works on instances
- Adding parentheses after class name
Given the following classes, how can you create a type alias EmployeeParams that matches the constructor parameters of Employee by reusing the constructor parameters of Person?
class Person {
constructor(public name: string, public age: number) {}
}
class Employee extends Person {
constructor(name: string, age: number, public salary: number) {
super(name, age);
}
}Solution
Step 1: Understand the constructor parameters
Personconstructor takesnameandage.Employeeaddssalaryas a third parameter.Step 2: Reuse Person's constructor parameters and add salary
UsingConstructorParameters<typeof Person>gives[string, number]. Addingnumberfor salary creates[string, number, number].Step 3: Check options
type EmployeeParams = [...ConstructorParameters<typeof Person>, number]; correctly uses tuple spread to combine parameters. type EmployeeParams = ConstructorParameters<typeof Employee>; gets all parameters but does not reuse Person's. type EmployeeParams = ConstructorParameters<Person> & number; is invalid syntax. type EmployeeParams = [string, number, number]; hardcodes types without reuse.Final Answer:
type EmployeeParams = [...ConstructorParameters<typeof Person>, number]; -> Option DQuick Check:
Reuse constructor params with tuple spread [OK]
- Not using typeof with class name
- Hardcoding parameter types instead of reusing
- Using invalid intersection (&) instead of tuple spread
Ready to prove it?
Pass the test and this pattern moves unknown
