-
Notifications
You must be signed in to change notification settings - Fork 151
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
GH 1357: Project caches should not accept arbitrary kwargs #1373
Conversation
Check out this pull request on You'll be able to see Jupyter notebook diff and discuss changes. Powered by ReviewNB. |
Codecov Report
@@ Coverage Diff @@
## rc/1.5.0 #1373 +/- ##
============================================
+ Coverage 34.53% 34.54% +0.01%
============================================
Files 342 342
Lines 33231 33262 +31
============================================
+ Hits 11475 11492 +17
- Misses 21756 21770 +14
Continue to review full report at Codecov.
|
95516df
to
ffea826
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.
Overall looks good to me.
Accepting arbitrary kwargs led to confusion for scientists accidentally passing incorrect keywords. This PR removes the ability to pass arbitrary kwargs to public Project cache constructors, to reduce the possibility of silent errors.
ffea826
to
4350828
Compare
Accepting arbitrary kwargs led to confusion for scientists
accidentally passing incorrect keywords. This PR removes
the ability to pass arbitrary kwargs to public Project cache
constructors, to reduce the possibility of silent errors.
In addition to unit-testing I ran quick notebook examples with all the different constructors (fixed, warehouse, lims, etc.). In doing so I noticed a typo in the keyword-argument of the ecephys example, and a failure in the behavior project cache notebook due to an oversight about which ID is used.