Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: Types no longer allow passing a named function to describe

See original GitHub issue

Version

27.0.6 and 28.0.0-alpha.4

Steps to reproduce

https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzgEwKYGcDGVgCNVwC+cAZlBCHAOQACAVhjAPQDmANhLgIZvpUDcAKEEkArgDtMMYBHFwQATwBiEqTLkAKAJSJCQwWiw58GxSsnTZAGjja4AXgB8urfyA

Expected behavior

No type errors on describe(myFunction, () => {})

Actual behavior

Argument of type '() => void' is not assignable to parameter of type 'string'.

Additional context

Allowing taking in class/function names in describe was added in #5154 and typed in @types/jest in https://github.com/DefinitelyTyped/DefinitelyTyped/pull/23102.

Tests still pass while taking in a name; it’s just the typings that are incorrect.

Environment

System:
    OS: Linux 5.10 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Binaries:
    Node: 16.13.0 - /usr/bin/node
    Yarn: 3.2.0 - /usr/local/bin/yarn
    npm: 8.1.0 - /usr/bin/npm
  npmPackages:
    jest: workspace:* => 28.0.0-alpha.4

Issue Analytics

State:
Created 2 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

SimenBcommented, Feb 24, 2022

https://github.com/facebook/jest/releases/tag/v28.0.0-alpha.5

0reactions

github-actions[bot]commented, Mar 27, 2022

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.