-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
refactor: QueryContext and QueryObject by decoupling and making it testable #17344
Conversation
bf701b4
to
4d99c4d
Compare
4d99c4d
to
1529bd0
Compare
…ss decouple from Superset
1529bd0
to
1ec2862
Compare
Codecov Report
@@ Coverage Diff @@
## master #17344 +/- ##
==========================================
- Coverage 77.14% 76.95% -0.19%
==========================================
Files 1036 1040 +4
Lines 55759 55892 +133
Branches 7628 7628
==========================================
- Hits 43013 43012 -1
- Misses 12490 12624 +134
Partials 256 256
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Note that this is super risky, because we don't have 100% unit test coverage. |
I agree , but on the other hand if we want to move towards better coverage we need to start refactoring and do separation of concerns |
I think if it's possible to split this change into smaller PRs, that will make it much more reviewable. Also, as the purpose of this PR is to make the code testable, I think it would be appropriate and necessary to add tests as part of the refactor. And if there are any additional tests that cover parts of this, would you mind linking to them? As a reviewer I find tests very helpful for understanding the code. |
326d64d
to
2cf689c
Compare
2cf689c
to
4fedf18
Compare
A preparation task for #16991.
decoupling QueryContext and QueryObject classes from superset so they can be used in unit tests and future usages.
What have done:
It relies on the current test cases since no logic was added
follows up: