TypeScript(error:2532): object may be undefined despite null or undefined check

Question

TypeScript(error:2532): object may be undefined despite null or undefined check

Currently, I am developing a Discord-bot using TypeScript which includes a command to retrieve information from an airport. To do this, users only need to provide the 4-character ICAO code that identifies the specific airport. However, due to potential user errors in inputting the ICAO code, I have implemented a method that retrieves the airport object from a JSON file. Here is a simplified representation of how the method looks:

public getAirport(icao: string): Airport | undefined {
    return arrayOfAllAirports.find(ap => ap.icao === icao);
}

In my command file/class, I utilize this method to fetch the airport based on the provided ICAO code. Subsequently, I check if the returned value is undefined and handle it accordingly by displaying an error message. This portion of the code appears as follows:

let airportMgr = new AirportManager();
    
let airport = airportMgr.getAirport(icao);
if (airport === undefined) {
    return *invalid ICAO error*;
}

*additional logic*

let exampleString = `ICAO: ${airport.icao} | Name: ${airport.name}`;
                                    ^error shown here             ^error shown here

On rare occasions, I encounter an error in two distinct files/classes where I use this particular method together with the defined checks. The error suggests that the 'airport' object may be undefined. Strangely, when accessing some other property of 'airport' a few lines below, no error is indicated.

While I could resolve this issue temporarily by utilizing as Airport when retrieving or reassigning the airport, I aim to identify a more robust solution rather than circumventing TypeScript rules. Can anyone provide insights on how to effectively address this perplexing problem?

edit:

A reference picture showing the area where the code worked correctly can be viewed here: https://i.stack.imgur.com/tTZyJ.png

typescript discord undefined

Answer 1

Answer №1

The issue lies in your use of let instead of const. When using let, the variable can be reassigned, potentially changing its type throughout the code. Here's an example to illustrate this concept:

// Making it async for demonstration purposes; adapt as needed
async function doStuff() {
  const icao = 'some icao';
  let airport: Airport | undefined = getAirport(icao);

  if (airport === undefined) {
    return;
  }

  // Exploring different scenarios based on lexical scope
  airport.name;

  // Function within current lexical scope
  function someHelperFunction() {
    airport.name;
  }

  // Promise resolution values don't retain original type
  Promise.resolve().then(() => {
    airport.name
  });

  // Works with simple awaits
  const anything = await Promise.resolve('something');
  airport.name;

  // Creating a constant of known type for consistency
  const airportForSure: Airport = airport;
  function someOtherHelperFunction() {
    airportForSure.name;
  }

  Promise.resolve().then(() => {
    airportForSure.name
  });

  airport = getAirport(icao); // Value change requires reevaluation
  
  airport.name; // Will not work post-reassignment
}

type Airport {
  icao: string;
  name: string;
}

// Placeholder for actual function implementation
declare function getAirport(icao: string): Airport | undefined;

Link to TypeScript playground

Answer 2

The issue lies in your use of let instead of const. When using let, the variable can be reassigned, potentially changing its type throughout the code. Here's an example to illustrate this concept:

// Making it async for demonstration purposes; adapt as needed
async function doStuff() {
  const icao = 'some icao';
  let airport: Airport | undefined = getAirport(icao);

  if (airport === undefined) {
    return;
  }

  // Exploring different scenarios based on lexical scope
  airport.name;

  // Function within current lexical scope
  function someHelperFunction() {
    airport.name;
  }

  // Promise resolution values don't retain original type
  Promise.resolve().then(() => {
    airport.name
  });

  // Works with simple awaits
  const anything = await Promise.resolve('something');
  airport.name;

  // Creating a constant of known type for consistency
  const airportForSure: Airport = airport;
  function someOtherHelperFunction() {
    airportForSure.name;
  }

  Promise.resolve().then(() => {
    airportForSure.name
  });

  airport = getAirport(icao); // Value change requires reevaluation
  
  airport.name; // Will not work post-reassignment
}

type Airport {
  icao: string;
  name: string;
}

// Placeholder for actual function implementation
declare function getAirport(icao: string): Airport | undefined;

Link to TypeScript playground

TypeScript(error:2532): object may be undefined despite null or undefined check

Answer №1

Similar questions

Error: In Typescript, it is not possible to assign the type 'false' to type 'true'

ERROR UnhandledTypeError: Unable to access attributes of null (attempting to retrieve 'pipe')

Variable type linked to interface content type

Customizing the output format of Ng Date Picker beyond the standard ISO-8601

Building a resolver to modify a DynamoDB item via AppSync using the AWS Cloud Development Kit (CDK)

Tips on how to retrieve a stubbed Observable<void> in RxJS

What is the best way to activate an input field in react-select?

Adjusting the background color of the custom input range thumb when the input is disabled

Code error TS2345 occurs when assigning the argument of type '{ headers: HttpHeaders; }' to a parameter of type 'RequestOptionsArgs'. This indicates a mismatch in the type of data being passed, causing an

Can Cloud Functions be used to establish a connection between Cloud Firestore and Realtime Database?

Using Angular's dependency injection in a project that has been transpiled with Babel

Ways to verify function arguments within an asynchronous function using Jest

Utilizing a loaded variable containing data from an external API request within the useEffect() hook of a React component

Switching from callback to function in TypeScript

tips for managing response time in firebase authentication state

Here are some steps to turn off browser autocomplete for a p-inputMask field

How do I assign a default value to an optional parameter in a derived class in Typescript?

Running cy.task after all test suites can be done by adding the task in a

What role does the @Input statement in the HeroDetailComponent class serve in the Angular 2 Quickstart tutorial?

What could be causing my for loop to not function properly within the ngOnInit lifecycle hook?