Loosen string comparison

[isidornygren]

As currently, it will fail if the types have a different amount of whitespaces, e.g if the checked type is { name: string, value: number } it will fail the check if the defined type is {name:string,value:number} which imo shouldn't fail, as it would be nice to be able to format the types in the comment nicer.
Especially if multiline type comments for complex types would work in the future, some kind of whitespace remover would definitely be needed.

[JakeSidSmith]

I'm reluctant to loosen the string comparison, as there is potential for types that do not match to pass, however, to make it easier to see where whitespace differs I have added/improved the output to highlight differences:

Would you say that this resolves this issue?

[JakeSidSmith]

Also, I just quite like that this is strict. Strict is what I always intended.

[isidornygren]

That's fine I guess.
What would happen if the type was really complex then? Would you have to write everything in one line?

const something = someFunc(); // { value: { inner: number, innerString: string}, someOtherValue: string, moreValue: { date: Date, isFuture: boolean, hasKetchup: boolean } }

[JakeSidSmith]

Yup. But you'd generally be pulling those inner parts out into their own types, so the assertions shouldn't really get that large, and instead end up with { value: InnerThing, someOtherValue: Something } or even just AllMyValues possibly with generics.