Strict configuration objects in Typescript

Introduction

Strict configuration objects help catch mistakes early by making sure only allowed settings are used.

When you want to make sure a function only accepts specific options.

When you want to avoid typos in configuration keys.

When you want to get helpful errors while coding instead of bugs later.

When you want to clearly document what settings are allowed.

When you want to prevent extra or unknown properties in objects.

Syntax

Typescript

function setup(config: { optionA: string; optionB: number }): void {
  // use config.optionA and config.optionB
}

Define the exact shape of the config object using an inline type or an interface.

TypeScript will check that only the specified keys are present.

Examples

This function only accepts an object with debug and maxRetries keys.

Typescript

function configure(settings: { debug: boolean; maxRetries: number }) {
  console.log(settings.debug, settings.maxRetries);
}

Using an interface to define the config shape makes the code cleaner and reusable.

Typescript

interface Config {
  url: string;
  timeout: number;
}

function connect(config: Config) {
  console.log(`Connecting to ${config.url} with timeout ${config.timeout}`);
}

Passing a strict config object ensures only allowed options are used.

Typescript

function start(options: { verbose: boolean }) {
  console.log(options.verbose ? 'Verbose mode on' : 'Verbose mode off');
}

start({ verbose: true });

Sample Program

This program defines a strict config object for server settings and prints the server address.

Typescript

interface ServerConfig {
  host: string;
  port: number;
}

function startServer(config: ServerConfig) {
  console.log(`Server running at http://${config.host}:${config.port}`);
}

startServer({ host: 'localhost', port: 8080 });

Important Notes

If you pass extra keys not defined in the config type, TypeScript will show an error.

Strict config objects help prevent bugs caused by misspelled or unexpected properties.

Summary

Strict configuration objects define exactly what settings are allowed.

They help catch errors early by checking object keys and types.

Use interfaces or inline types to create strict configs in TypeScript.

Practice

1.

What is the main benefit of using strict configuration objects in TypeScript?

easy

A. They allow any keys to be added without errors.

B. They make the code run faster at runtime.

C. They catch errors early by enforcing exact keys and types.

D. They automatically generate UI forms for settings.

Solution

1. Step 1: Understand strict configuration objects

   Strict configs define exactly which keys and types are allowed in an object.

2. Step 2: Identify the main benefit

   This strictness helps catch mistakes early, before running the code.

3. Final Answer:

   They catch errors early by enforcing exact keys and types. -> Option C

4. Quick Check:

   Strict config = early error detection [OK]

Hint: Strict configs prevent wrong keys and types early [OK]

Common Mistakes:

• Thinking strict configs improve runtime speed
• Believing strict configs allow any keys
• Confusing strict configs with UI generation

2.

Which of the following is the correct way to declare a strict configuration object type in TypeScript?

interface Config {
  host: string;
  port: number;
}

easy

A. const config: Config = { host: 'localhost', port: 8080 };

B. const config: Config = { host: 'localhost' };

C. const config: Config = { host: 'localhost', port: '8080' };

D. const config = { host: 'localhost', port: 8080 };

Solution

1. Step 1: Check interface requirements

   The Config interface requires both 'host' as string and 'port' as number.

2. Step 2: Match object to interface

   const config: Config = { host: 'localhost', port: 8080 }; has both keys with correct types, so it matches Config exactly.

3. Final Answer:

   const config: Config = { host: 'localhost', port: 8080 }; -> Option A

4. Quick Check:

   All required keys with correct types = const config: Config = { host: 'localhost', port: 8080 }; [OK]

Hint: Match all keys and types exactly to interface [OK]

Common Mistakes:

• Omitting required keys
• Using wrong types for keys
• Not specifying the type annotation

3.

What will be the output of this TypeScript code?

interface Settings {
  debug: boolean;
  version: string;
}

const config: Settings = { debug: true, version: '1.0' };
console.log(config.debug, config.version);

medium

A. true 1.0

B. true '1.0'

C. undefined undefined

D. Error: Missing properties

Solution

1. Step 1: Check object matches interface

   The object has 'debug' as true (boolean) and 'version' as '1.0' (string), matching Settings.

2. Step 2: Understand console.log output

   console.log prints the boolean true and string '1.0' without quotes, so output is: true 1.0

3. Final Answer:

   true 1.0 -> Option A

4. Quick Check:

   Matching keys print their values correctly [OK]

Hint: Check object keys match interface and print values directly [OK]

Common Mistakes:

• Expecting quotes around string in console output
• Thinking missing keys cause runtime error
• Confusing type errors with runtime output

4.

Identify the error in this TypeScript code using a strict configuration object:

interface Options {
  timeout: number;
  verbose: boolean;
}

const opts: Options = { timeout: 5000, verbose: 'yes' };

medium

A. Property 'timeout' is missing.

B. Property 'verbose' should be a boolean, not a string.

C. Extra property 'verbose' is not allowed.

D. No error, code is correct.

Solution

1. Step 1: Check property types against interface

   'timeout' is number 5000, correct. 'verbose' is string 'yes', but interface requires boolean.

2. Step 2: Identify type mismatch error

   Assigning string to boolean property causes a type error.

3. Final Answer:

   Property 'verbose' should be a boolean, not a string. -> Option B

4. Quick Check:

   Type mismatch on 'verbose' property [OK]

Hint: Check each property type matches interface exactly [OK]

Common Mistakes:

• Ignoring type mismatch errors
• Thinking missing properties cause this error
• Confusing extra properties with wrong types

5.

You want to create a strict configuration object that only allows keys mode (string), retry (number), and enabled (boolean). Which TypeScript type definition ensures no extra keys are allowed?

hard

A. interface Config { mode: string; retry: number; enabled: boolean; }

B. type Config = { mode: string; retry: number; enabled: boolean; [key: string]: any }

C. type Config = { mode?: string; retry?: number; enabled?: boolean }

D. interface Config { mode: string; retry: number; enabled: boolean; [key: string]: never }

Solution

1. Step 1: Understand how to forbid extra keys

   Using an index signature with [key: string]: never forbids any keys not explicitly declared.

2. Step 2: Compare options

   interface Config { mode: string; retry: number; enabled: boolean; } allows extra keys implicitly. type Config = { mode: string; retry: number; enabled: boolean; [key: string]: any } allows any extra keys. type Config = { mode?: string; retry?: number; enabled?: boolean } makes keys optional but doesn't forbid extras. Only interface Config { mode: string; retry: number; enabled: boolean; [key: string]: never } forbids extra keys.

3. Final Answer:

   interface Config { mode: string; retry: number; enabled: boolean; [key: string]: never } -> Option D

4. Quick Check:

   Index signature with never forbids extra keys [OK]

Hint: Use [key: string]: never to forbid extra keys [OK]

Common Mistakes:

• Thinking interface alone forbids extra keys
• Using any type index signature allowing extras
• Making keys optional but not forbidding extras