feat: assertion functions

[woutermont]

Signed-off-by: Wouter Termont [email protected]

[lem-onade]

Looks good.

Consider the following:

let variable: string;
variable = functionThatMightReturnUndefined();
assert(!isUndefined(variable)); // yes?
someOtherFunction(variable); // this function's param is required

Will TS complain about someOtherFunction having an object that is possibly undefined or does it recognize it can't be after the assert (the same way a simple if (!variable) does)? Asking because I've had to put in a lot of these ifs lately by enabling strict mode in NDE's core package. (most of the inrupt sdk's data function return Thing | null)

[lem-onade]

Not related to this PR in specific but these .npmrc files can be removed if we all npm login once with the access token which is currently in $NPM_TOKEN

(https://github.com/netwerk-digitaal-erfgoed/solid-crs/blob/master/docs/modules/manual/pages/install.adoc#configure-git)

[woutermont]

Does that go for all .nmprc files?

[lem-onade]

All .npmrc files, but looks like they should still exist, just not contain the authToken stuff.
See https://github.com/netwerk-digitaal-erfgoed/solid-crs/blob/master/.npmrc

[lem-onade]

But should probably be its own issue in another repo (or all repos)

[woutermont]

About your example, @lem-onade: while you'll probably have to use assert(not(isUndefined(variable))), or some sugar like assert(isDefined(variable)) which I can easily add, the answer to your question is 'yes', TS will indeed now that it is defined after the assert.