functional/no-mixed-types fails when a function type is aliased using typeof

[apolishch]

Bug Report

no-mixed-types fails when a function type is aliased as part of a larger object type

Expected behavior

aliases are understood correctly

Actual behavior

functional/no-mixed-types fails with:

error Only the same kind of members allowed in types

Steps to reproduce

const func = (v: any): any => null
type foo = typeof func

type foobar = Readonly<{
    foo1: (v: any) => null,
    foo2: foo
}>

Proposed changes

I've had to turn off the rule for the time being unfortunately :(

[github-actions]

🎉 This issue has been resolved in version 6.2.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀