Skip to content

RequiredDeep silently erases types past a depth of 3 as a side-effect #677

Description

@ahrjarrett

See this issue, specifically this comment.

Using a recursively mapped type like RequiredDeep comes with a side effect: even though VS Code seems to resolve the type, the type-checker ignores anything past a depth of 3.

Note that it's quite difficult to identify that type-checking is not happening at all, since there's still no indication by looking at the types that they don't actually check anything.

Users are almost certainly unaware that by using recursively mapped types like RequiredDeep, they are effectively turning off the type checker.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions