-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
feat: SQLA factory #369
feat: SQLA factory #369
Conversation
Few points:
|
Yep, can do. Note I did not have permissions to push to the existing branch so made a new branch. |
* feat: Add SQLAlchemyFactory table column parsing * docs: Add SQLAlchemy reference * docs: amend link * doc: amend link * Revert type updates * feat: add SQLAlchemy relationship configuration * feat: improve mapping for SQLAlchemy ARRAY * feat: SQLAlchemy test hints for 3.8 * feat: SQLAlchemy test hints for 3.8 * feat: SQLAlchemy test hints for 3.8 * feat: SQLAlchemy factory hints for 3.8 * feat: add extra attributes for SQLAlchemyFactory * feat: resolve SQLAlchemyFactory type issues * feat: fix rebase errors
0d89d72
to
ad5a267
Compare
83638a1
to
a91c564
Compare
a91c564
to
fb38107
Compare
@adhtruong does this work for SQLA v1? If so, can you add tests specifically for v1 and add pytest markers skipping the v2 tests if in v1 and skipping v1 tests if in v2? |
Nevermind. I just saw that you've kept |
This feels reasonable to support. I tried locally and implementation on factory currently works with SQLA1.4. I'll update the bounds and CI to test this. |
This is a bit more involved due to some typing issues. Happy for this to be left to a separate issue/PR? |
Great work @adhtruong! |
Yupp that's fine. |
@all-contributors add @adhtruong for docs, test, code |
I've put up a pull request to add @adhtruong! 🎉 |
Pull Request Checklist
Description
Close Issue(s)