-
-
Notifications
You must be signed in to change notification settings - Fork 330
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
chore: unpin Advanced Alchemy #3491
Conversation
For the 3.8 failure, you'd either have to update the AA pagination class to use the typing generic collection types (ie |
Thanks - Just saw this as I came to the same conclusions. Resolved in litestar-org/advanced-alchemy#191 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3491 +/- ##
==========================================
- Coverage 98.30% 98.30% -0.01%
==========================================
Files 328 328
Lines 14884 14875 -9
Branches 2366 2365 -1
==========================================
- Hits 14632 14623 -9
Misses 115 115
Partials 137 137 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Peter Schutt <peter.github@proton.me>
Quality Gate passedIssues Measures |
Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/3491 |
Description
This PR unpins Advanced Alchemy.
This allows version
0.9.3
to be installed with tehlitestar[sqlalchemy]
command group.This enables the following:
to_schema
from theService
used there (see the fullstack repository for usage details)However, this AA release also had to integrate it's own copies of the Litesatr
OffsetPagination
dataclass. Litestar will attempt to use this version of the dataclass when a supported version is installed. This is implemented similar to how the filters infilters.py
work currently.Closes