-
Notifications
You must be signed in to change notification settings - Fork 26
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
Enable default component arguments #199
Conversation
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.
Thanks @PhilippeMoussalli, just some suggestions to make the documentation more clear.
fondant/component.py
Outdated
return parser.parse_args() | ||
@staticmethod | ||
def optional_fondant_arguments() -> t.List[str]: | ||
return [] |
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 would expect the output_manifest_path
here
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.
good catch, will change it
Co-authored-by: Robbe Sneyders <[email protected]>
Co-authored-by: Robbe Sneyders <[email protected]>
PR that enables adding default arguments as discussed in #179. Users can now define default arguments in the component specs. Those arguments do not have to be explicitly defined in the `ComponentOp` but could still be overridden. Note: please review this [PR](#196) beforehand since I am branched off from it. Created a separate ticket to do the necessary changes #198. Best to handle it in a separate PR. --------- Co-authored-by: Robbe Sneyders <[email protected]>
PR that enables adding default arguments as discussed in #179.
Users can now define default arguments in the component specs. Those arguments do not have to be explicitly defined in the
ComponentOp
but could still be overridden.Note: please review this PR beforehand since I am branched off from it.
Created a separate ticket to do the necessary changes #198. Best to handle it in a separate PR.