-
Notifications
You must be signed in to change notification settings - Fork 320
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
add function to get guids by run spec #3863
add function to get guids by run spec #3863
Conversation
d862a42
to
b97fda9
Compare
Codecov Report
@@ Coverage Diff @@
## master #3863 +/- ##
=======================================
Coverage 65.77% 65.78%
=======================================
Files 228 228
Lines 31103 31113 +10
=======================================
+ Hits 20459 20468 +9
- Misses 10644 10645 +1 |
@jenshnielsen this looks good to me. The only thing that I think is worth considering is what we do about the |
So we want to leave the code for querying in that module but we could rename the get_guids_from_run_spec in that module to something else |
b97fda9
to
beb2b94
Compare
@astafan8 Can you see if this api makes sense. If so I will finish this up with some tests |
beb2b94
to
d2ebbc7
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.
yes, the API looks good!
d2ebbc7
to
50e07a9
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.
@jenshnielsen so we are basically renaming the function because we have connection as a non-keyword argument, right? I think it does make a lot of sense to me, how you implemented this change.
@Dominik-Vogel yes and also to match load_by_id, load_by_run_spec etc |
bors merge |
And deprecate and remove use of get_guids_from_run_spec.