-
Notifications
You must be signed in to change notification settings - Fork 90
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
get_output_schema exception with table name #449
get_output_schema exception with table name #449
Conversation
…ponding table if something goes wrong while generating the tables.
The test works in python 3.10 (and 3.9 in local) but not with 3.7. |
I think something changed with mocks in > Python 3.7. I've been caught out by this many times. |
https://docs.python.org/3/library/unittest.mock.html#unittest.mock.AsyncMock I think this is it. |
@AliSayyah If you search for |
Codecov Report
@@ Coverage Diff @@
## master #449 +/- ##
==========================================
- Coverage 90.84% 90.74% -0.11%
==========================================
Files 103 104 +1
Lines 6870 6902 +32
==========================================
+ Hits 6241 6263 +22
- Misses 629 639 +10
Continue to review full report at Codecov.
|
@dantownsend I think this is ready for review, |
@AliSayyah Cool, thanks |
@AliSayyah This looks great thanks. I pushed a few extra commits:
|
Thank you this is great! |
@AliSayyah Yeah, it could do with a unit test really. I'm happy to release as is, but if you wouldn't mind doing a separate PR to add a test, that would be great. |
Yeah, I'll open another PR👍. |
@AliSayyah thanks |
get_output_schema will raise an exception with the name of the corresponding table if something goes wrong while generating the tables.
based on #447
Another alternative would be to add the
errors
attribute to theOutputSchema
class and handle it like how warnings are being addressed.