caseError fails with Tasks rejected with only one possible type

[dggluz]

In this case:

class NoNegativesError extends Error {
	NoNegativesError = 'NoNegativesError';
}

const rejectNegative = (x: number): Task<number, NoNegativesError> =>
	x >= 0 ?
		Task.resolve(x) :
		Task.reject(new NoNegativesError())
;

const aNumber = rejectNegative(9);

const fixNoNegativesError = caseError(NoNegativesError, _ => Task.resolve(0));

const result = aNumber.catch(fixNoNegativesError);

We expect result to be a Task<number, UncaughtError> but it is a Task<number, NoNegativesError | UncaughtError>. If we had:

const aNumber = rejectNegative(9).map(x => x);

the result would have been the expected one.

This bug is associated with caseError and happens only with Tasks rejected with only one type.

[hrajchert]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀