3.0.4 • Published 2 years ago

erreur v3.0.4

Weekly downloads
-
License
MIT
Repository
github
Last release
2 years ago

🛑 Erreur

Type safe custom errors

Type safe custom errors ?

This librairy expose a way to define and manipulate custom errors in a type safe way.

To acheive this, it uses a class called Erreur (error in french) that extends the native Error class. This class can contain data but in order to ensure type safety, you cannot access this data directly. Instead, you must use a declaration that can be created using the createKey.

Internally, the Erreur class uses etienne-dldc/staack to store the data.

Here is a simple example:

import { ErreurType, Erreur } from 'erreur';

// Create a new type
const HttpErrorType = ErreurType.define<number>('StatusCode');

// Create a new Erreur
const err = Erreur.create('Something went wrong');

// Add data to the Erreur
const errWithStatusCode = HttpErrorType.extends(err, 500);

// Get data from the Erreur
const statusCode = errWithStatusCode.get(HttpErrorType.Consumer);

expect(statusCode).toBe(500);

API

Erreur.create

Create a new Erreur instance. You can optionally pass a message:

const err1 = Erreur.create();
const err2 = Erreur.create('Something went wrong');

erreur.with(...providers)

Use the with method to add data to an Erreur instance. This method accepts any number of Provider declaration and returns a new Erreur instance:

const MyKey = createKey<string>({ name: 'MyKey' });

const err1 = Erreur.create().with(MyKey.Provider('Hello'));

erreur.get(consumer)

erreur.getOrFail(consumer)

erreur.has(consumer)

Erreur.is

Check if a value is an Erreur instance:

const err = Erreur.create();
const isErr = Erreur.is(err); // true

Note: this is the same as using instanceof Erreur

Erreur.wrap and Erreur.wrapAsync

Wrap a function to make sure it either returns a value or throws an Erreur instance. Not that this function does not care about what is inside the Erreur instance, it only checks that it is an instance of Erreur.

Erreur.resolve and Erreur.resolveAsync

Same as Erreur.wrap and Erreur.wrapAsync but returns the Erreur instance instead of throwing it.

Overriding the message

You can override the message of an Erreur using the Erreur.MessageKey key:

const err1 = Erreur.create('Something went wrong');
const err2 = err1.with(Erreur.MessageKey.Provider('Something went really wrong'));
// A shortcut is also available
const err3 = err2.withMessage('Something went really wrong');

Recipes

Using Union types

You can handle many errors with a single key using union types:

type FetchError =
  | { type: 'NetworkError'; error: any }
  | { type: 'ParseError'; content: string }
  | { type: 'ResponseNotOk'; response: any };

const FetchErrorType = createErrorType<FetchError>({ name: 'FetchError' });
3.0.0-13

2 years ago

3.0.0-11

2 years ago

3.0.0-7

2 years ago

3.0.0-12

2 years ago

3.0.0-9

2 years ago

3.0.0-10

2 years ago

3.0.0-8

2 years ago

3.0.4

2 years ago

3.0.3

2 years ago

3.0.2

2 years ago

3.0.1

2 years ago

3.0.0

2 years ago

3.0.0-6

2 years ago

3.0.0-1

2 years ago

3.0.0-0

2 years ago

3.0.0-3

2 years ago

3.0.0-2

2 years ago

3.0.0-5

2 years ago

3.0.0-4

2 years ago

2.1.0

2 years ago

2.0.0

2 years ago

2.0.0-12

2 years ago

2.0.0-11

2 years ago

2.0.0-10

2 years ago

2.0.0-9

2 years ago

2.0.0-8

2 years ago

2.0.0-7

2 years ago

2.0.0-6

2 years ago

2.0.0-5

2 years ago

2.0.0-4

2 years ago

2.0.0-3

2 years ago

2.0.0-2

2 years ago

2.0.0-1

2 years ago

2.0.0-0

2 years ago

1.1.1

2 years ago

1.1.0

2 years ago

1.0.2

2 years ago

1.0.1

2 years ago

1.0.0

2 years ago