Skip to content

Fix type checker error #378

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 8, 2023
Merged

Conversation

layday
Copy link
Contributor

@layday layday commented Jun 7, 2023

Pyright expects typing.Type to be parameterised and reports that the function's type is unknown.

@codecov-commenter
Copy link

codecov-commenter commented Jun 7, 2023

Codecov Report

Merging #378 (5940921) into main (dedd72d) will not change coverage.
The diff coverage is 100.00%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main     #378   +/-   ##
=======================================
  Coverage   95.80%   95.80%           
=======================================
  Files          26       26           
  Lines        2121     2121           
=======================================
  Hits         2032     2032           
  Misses         89       89           
Impacted Files Coverage Δ
src/cattrs/v.py 91.66% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@Tinche
Copy link
Member

Tinche commented Jun 7, 2023

LGTM, let's just add a small changelog snippet.

layday added 2 commits June 8, 2023 02:15
Pyright expects `typing.Type` to be parameterised and reports that
the function's type is unknown.
@layday layday force-pushed the fix-type-error-in-pyright branch from 985e22e to 5940921 Compare June 7, 2023 23:17
@Tinche
Copy link
Member

Tinche commented Jun 8, 2023

Thanks!

@Tinche Tinche merged commit 116d25b into python-attrs:main Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants