TypeScript filter out nulls from an array

TypescriptNull

Typescript Problem Overview


TypeScript, --strictNullChecks mode.

Suppose I have an array of nullable strings (string | null)[]. What would be a single-expression way to remove all nulls in a such a way that the result has type string[]?

const array: (string | null)[] = ["foo", "bar", null, "zoo", null];
const filterdArray: string[] = ???;

Array.filter does not work here:

// Type '(string | null)[]' is not assignable to type 'string[]'
array.filter(x => x != null);

Array comprehensions could've work but they are not supported by TypeScript.

Actually the question can be generalized to the problem of filtering an array of any union type by removing entries having one particular type from the union. But let's focus on unions with null and perhaps undefined as these are the most common usecases.

Typescript Solutions


Solution 1 - Typescript

You can use a type predicate function in the .filter to avoid opting out of strict type checking:

function notEmpty<TValue>(value: TValue | null | undefined): value is TValue {
    return value !== null && value !== undefined;
}

const array: (string | null)[] = ['foo', 'bar', null, 'zoo', null];
const filteredArray: string[] = array.filter(notEmpty);

Alternatively you can use array.reduce<string[]>(...).

2021 update: stricter predicates

While this solution works in most scenarios, you can get a more rigorous type check in the predicate. As presented, the function notEmpty does not actually guarantee that it identifies correctly whether the value is null or undefined at compile time. For example, try shortening its return statement down to return value !== null;, and you'll see no compiler error, even though the function will incorrectly return true on undefined.

One way to mitigate this is to constrain the type first using control flow blocks, and then to use a dummy variable to give the compiler something to check. In the example below, the compiler is able to infer that the value parameter cannot be a null or undefined by the time it gets to the assignment. However, if you remove || value === undefined from the if condition, you will see a compiler error, informing you of the bug in the example above.

function notEmpty(value: TValue | null | undefined): value is TValue { if (value === null || value === undefined) return false; const testDummy: TValue = value; return true; }

A word of caution: there exist situations where this method can still fail you. Be sure to be mindful of issues associated with contravariance.

Solution 2 - Typescript

Similar to @bijou-trouvaille's answer, you just need to declare the <arg> is <Type> as the output of the filter function:

array.filter((x): x is MyType => x !== null);

Solution 3 - Typescript

One more for good measure as people often forget about flatMap which can handle filter and map in one go (this also doesn't require any casting to string[]):

// (string | null)[]
const arr = ["a", null, "b", "c"];
// string[]
const stringsOnly = arr.flatMap(f => f ? [f] : []);

Solution 4 - Typescript

One liner:

const filteredArray: string[] = array.filter((s): s is string => Boolean(s));

TypeScript playground

The trick is to pass a type predicate (:s is string syntax).

This answer shows that Array.filter requires users to provide a type predicate.

Solution 5 - Typescript

You can cast your filter result into the type you want:

const array: (string | null)[] = ["foo", "bar", null, "zoo", null];
const filterdArray = array.filter(x => x != null) as string[];

This works for the more general use case that you mentioned, for example:

const array2: (string | number)[] = ["str1", 1, "str2", 2];
const onlyStrings = array2.filter(x => typeof x === "string") as string[];
const onlyNumbers = array2.filter(x => typeof x === "number") as number[];

(code in playground)

Solution 6 - Typescript

To avoid everybody having to write the same type guard helper functions over and over again I bundled functions called isPresent, isDefined and isFilled into a helper library: https://www.npmjs.com/package/ts-is-present

The type definitions are currently:

export declare function isPresent<T>(t: T | undefined | null): t is T;
export declare function isDefined<T>(t: T | undefined): t is T;
export declare function isFilled<T>(t: T | null): t is T;

You can use this like so:

import { isDefined } from 'ts-is-present';

type TestData = {
  data: string;
};

const results: Array<TestData | undefined> = [
  { data: 'hello' },
  undefined,
  { data: 'world' }
];

const definedResults: Array<TestData> = results.filter(isDefined);

console.log(definedResults);

When Typescript bundles this functionality in I'll remove the package. But, for now, enjoy.

Solution 7 - Typescript

Here is a solution that uses NonNullable. I find it even a little bit more concise than the accepted answer by @bijou-trouvaille

function notEmpty<TValue>(value: TValue): value is NonNullable<TValue> {
    return value !== null && value !== undefined;
}
const array: (string | null | undefined)[] = ['foo', 'bar', null, 'zoo', undefined];

const filteredArray: string[] = array.filter(notEmpty);
console.log(filteredArray)
[LOG]: ["foo", "bar", "zoo"]

Solution 8 - Typescript

If you already use Lodash, you can use compact. Or, if you prefer Ramda, the ramda-adjunct has also compact function.

Both have types, so your tsc will be happy and get the correct types as a result.

From Lodash d.ts file:

/**
 * Creates an array with all falsey values removed. The values false, null, 0, "", undefined, and NaN are
 * falsey.
 *
 * @param array The array to compact.
 * @return Returns the new array of filtered values.
 */
compact<T>(array: List<T | null | undefined | false | "" | 0> | null | undefined): T[];

Solution 9 - Typescript

I believe you have it all good except that the type checking just makes the filtered type not be different than the return type.

const array: (string | null)[] = ["foo", "bar", null, "zoo", null];
const filterdArray: string[] = array.filter(f => f !== undefined && f !== null) as any;
console.log(filterdArray);

Solution 10 - Typescript

I think this will be an easy approach, with more cleaner code

const array: (string | null)[] = ['foo', 'bar', null, 'zoo', null];
const filteredArray: string[] = array.filter(a => !!a);

Solution 11 - Typescript

simply use

array.filter(Boolean);

This will work for all truth values.

This, unfortunately, do not provide type inference, found this solution on here


type Truthy<T> = T extends false | '' | 0 | null | undefined ? never : T; //from lodash 

function truthy<T>(value: T): value is Truthy<T> {
    return Boolean(value);  //  or !!value
}

const arr =["hello","felow","developer","",null,undefined];

const truthyArr = arr.filter(truthy);

// the type of truthyArr will be string[]

Solution 12 - Typescript

const filterdArray = array.filter(f => !!f) as string[];

Solution 13 - Typescript

If you are checking null with other conditions using filter simply this can be used hope this helps for some one who is looking solutions for an object array

array.filter(x => x != null);
array.filter(x => (x != null) && (x.name == 'Tom'));

Solution 14 - Typescript

TypeScript has some utilities to infer the type of the array and exclude the null values from it:

const arrayWithNulls = ["foo", "bar", null, "zoo", null]

type ArrayWithoutNulls = NonNullable<typeof arrayWithNulls[number]>[]

const arrayWithoutNulls = arrayWithNulls.filter(x => x != null) as ArrayWithoutNulls

Longer but safer than just manually casting as string[] on your new array.

Step by step:

  1. Get the types from the original array:
typeof arrayWithNulls[number] // => string | null
  1. Exclude the null values:
NonNullable<typeof arrayWithNulls[number]> // => string
  1. Make it an array:
NonNullable<typeof arrayWithNulls[number]>[] // => string[]

Links:

Solution 15 - Typescript

Using reduce

Some answers suggest reduce, here is how:

const languages = ["fr", "en", undefined, null, "", "de"]

// the one I prefer:
languages.reduce<string[]>((previous, current) => current ? [...previous, current] : previous, [])

// or
languages.reduce((previous, current) => current ? [...previous, current] : previous, Array<string>())

// or
const reducer = (previous: string[], current: string | undefined | null) => current ? [...previous, current] : previous
languages.reduce(reducer, [])

Result: ["fr", "en", "de"]

TS Playground here.

Solution 16 - Typescript

I've come back to this question many times hoping some new Typescript feature or typing may fix it.

Here's a simple trick I quite like for when combining map with a subsequent filter.

const animals = ['cat', 'dog', 'mouse', 'sheep'];

const notDogAnimals = animals.map(a => 
{
   if (a == 'dog')
   {
      return null!;   // just skip dog
   }
   else {
      return { animal: a };
   }
}).filter(a => a);

You'll see I'm returning null! which actually becomes type never - meaning that the final type doesn't have null.

This is a slight variation on the original question but I find myself in this scenario quite often and it helps avoid another method call. Hopefully someday Typescript will come up with a better way.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSergeySView Question on Stackoverflow
Solution 1 - TypescriptBijou TrouvailleView Answer on Stackoverflow
Solution 2 - TypescriptalukachView Answer on Stackoverflow
Solution 3 - TypescriptMike SukmanowskyView Answer on Stackoverflow
Solution 4 - TypescriptDLightView Answer on Stackoverflow
Solution 5 - TypescriptNitzan TomerView Answer on Stackoverflow
Solution 6 - TypescriptRobert MassaioliView Answer on Stackoverflow
Solution 7 - TypescriptMathias DpunktView Answer on Stackoverflow
Solution 8 - TypescriptDavidView Answer on Stackoverflow
Solution 9 - TypescriptDigvijayView Answer on Stackoverflow
Solution 10 - TypescriptSourodeep ChatterjeeView Answer on Stackoverflow
Solution 11 - Typescriptshrijan tripathiView Answer on Stackoverflow
Solution 12 - TypescriptAlan DraperView Answer on Stackoverflow
Solution 13 - TypescriptAkitha_MJView Answer on Stackoverflow
Solution 14 - TypescriptGG.View Answer on Stackoverflow
Solution 15 - TypescriptfrouoView Answer on Stackoverflow
Solution 16 - TypescriptSimon_WeaverView Answer on Stackoverflow