-
-
Notifications
You must be signed in to change notification settings - Fork 389
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
fix(repositories): fix #2358 by re-exporting filters and exceptions from advanced-alchemy #2360
Conversation
0dd5d74
to
98a8ef0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I think we should probably remove the imports in advanced-alchemy that try to import the filters from Litestar first. Otherwise we might run into a circular import here. |
@provinzkraut @v3ss0n I think this one may be ready for a final review. I've removed the exports from |
…rom advanced-alchemy Signed-off-by: Janek Nouvertné <[email protected]>
Signed-off-by: Janek Nouvertné <[email protected]>
Signed-off-by: Janek Nouvertné <[email protected]>
5d0c0b5
to
9c6112e
Compare
Kudos, SonarCloud Quality Gate passed! |
Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/2360 |
Fixes #2358 by adding some missing re-exports from advanced-alchemy.