fix(typing): Correctly handle typing_extensions.TypeAliasType on typing-extensions>4.13.0 (fix #4088)#4089
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4089 +/- ##
=======================================
Coverage 98.34% 98.34%
=======================================
Files 348 348
Lines 15829 15833 +4
Branches 1749 1749
=======================================
+ Hits 15567 15571 +4
Misses 125 125
Partials 137 137 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
4cbdbf9 to
6049ef2
Compare
|
Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/4089 |
sobolevn
left a comment
There was a problem hiding this comment.
Thanks!
optional: I would also test type keyword, it also creates a TypeAliasType object, but just to be sure.
We have a separate test case for that! :) litestar/tests/unit/test_typing.py Lines 491 to 497 in bf86f7e |
TypeAliasTypeintroduced in typing-extensions4.13.0; This type is no longer backwards compatible, as it is a distinct new type fromtyping.TypeAliasType. We need to check for both types nowtyping-extensions