Rebecca Stevens

It's looking like TypeScript's type engine can't currently fully support this. Using the changes of the PR in it current state in conjunction with the overloads method should improve types...

We'll keep this open for now. I'll look into it some more to see if it's feasible. I'll close it if it becomes not viable.

@vitaly-t This one is ready to go.

The typeguard info is lost because the wrapper function is not a typeguard. If you simply make your wrapper function a typeguard then problem fixed. e.g. ```ts items.filter((num): num is...

I haven't looked too closely at the rule but I believe currently the rule doesn't use type information. It might be best to use an option to ignore typeguards so...

Here's how the new setup will work: ```ts const globalVar: { foo: string } = ...; // No error as this doesn't get checked. ``` ```ts type MutableFoo = {...

Yeah, that's right (interfaces are also covered by `type-declaration-immutableness`)

@jonaskello We already to release this?

They probably could be merged into one, but I think it would be best to keep them separate. The main reason for this is that `prefer-immutable-types` is about flagging inline...

Yeah, I was planning on doing manual write of the release notes for 5.0 rather than using the automated ones. I was just going to use the automated ones for...