-
Notifications
You must be signed in to change notification settings - Fork 5
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
MAINT: Refactor to use factory pattern #146
MAINT: Refactor to use factory pattern #146
Conversation
927b674
to
31ac81e
Compare
This dataclass will be used to store query blocks
this is a better suited name since these classes only hold mapping info fixup mapping interface
Remove QueryWrapper, use QueryFactory to create a QueryAPI object using QueryComponents Dataclass Move QueryAPI to api sub-module Add QueryBlocks as a way of accessing Query Objects in similar manner as before
update import paths mostly
refactor query_api tests, add tests for new classes
31ac81e
to
555782a
Compare
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #146 +/- ##
==========================================
+ Coverage 97.16% 97.17% +0.01%
==========================================
Files 134 142 +8
Lines 5925 6128 +203
Branches 404 410 +6
==========================================
+ Hits 5757 5955 +198
- Misses 138 144 +6
+ Partials 30 29 -1
☔ View full report in Codecov by Sentry. |
Needs tests for Mappings |
142c9b6
to
9c64e43
Compare
bc33ccc
to
709bc95
Compare
checks mappings are expected for each query mappings class
709bc95
to
4cb8a20
Compare
I've added client-side mapping tests - and altered server-side tests to ensure that there is an equivalent client-side test (to allow queries using |
change to now use a factory pattern to create queries
decouple query mappings and query components from queries
This will make chaining from one query to another easier