Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Modularize default load and save argument handling #15
Modularize default load and save argument handling #15
Changes from 11 commits
b9bf25d
ba18548
41b40b2
c10a654
bf2643f
e83502c
63fda57
0505773
a93abf2
4226c2e
a17ae9e
f7b2373
124d663
d3c7153
da10346
cac0c78
681beb0
0d31b7c
473d725
2a575d6
5896daa
3931744
b2e4c1c
184d9f7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I prefer calling
super
at the top of the constructor, so the subclass would overwrite stuff from the parent, as a "specialisation" of the superclass.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.
Fair argument. I just left it in the same place where default arguments were previously handled (as close to the original as I could), but that makes sense.
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.
Why this (and all other datasets in
kedro.io
that are eligible) are not inheriting from the newMixIn
? (maybe I missed something here, sorry about that!)The code feels inconsistent now (+ all this duplication can go away!)
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.
@tsanikgr #14 (comment)
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.
OK thanks! @idanov, since the mix in was introduced, and is solving the problem "of the wrong abstraction", should we just leverage it in the core datasets as well?
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.
@idanov @tsanikgr @tolomea Let me know what you all decide as the core team here; I’m OK with it as is (a current marginal improvement to
core
with potential to move the mix-in fromcontrib
after proving value in the future) or pushing the mix-in tocore
now. I’m more keen on merging todevelop
sooner than later due to the number of datasets touched, if possible. :)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.
I think the current version is good for now. Thanks @deepyaman for accommodating for all the comments!