-
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
Update core package #653
Update core package #653
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 @mrchtr! I did a first quick review.
I would focus on getting the core
module ported first and make sure the tests for those are passing. So everything related to the component spec and manifest.
Could you remove all the other changes from this branch and open those as PRs to this one? That would make it a lot easier to review :)
6bb9aa0
to
d8ecd01
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.
Thanks @mrchtr, clean work!
I still need to review the tests. I would split the test examples per module as well though.
Co-authored-by: Robbe Sneyders <[email protected]>
Co-authored-by: Robbe Sneyders <[email protected]>
Co-authored-by: Robbe Sneyders <[email protected]>
Co-authored-by: Robbe Sneyders <[email protected]>
Co-authored-by: Robbe Sneyders <[email protected]>
Co-authored-by: Robbe Sneyders <[email protected]>
I've cleaned the test a bit more. I moved the relevant sample files into |
src/fondant/core/manifest.py
Outdated
else: | ||
self._specification["fields"][field.name] = { | ||
"location": f"/{self.component_id}", | ||
"type": field.type.name, |
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.
See my comment below. We should store them as json mainly to match the format of the component spec
"type": field.type.name, | |
"type": field.type.to_json(), |
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! Wasn't aware of this, but it makes totally 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.
This broke some of the tests though.
>>> type.to_json()
{
"type": type
}
So now we get:
{
"location": ...,
"type": {
"type": type
}
}
I think we can solve it like this:
self._specification["fields"][field.name] = {
"location": f"/{self.component_id}",
**field.type.name,
}
Co-authored-by: Philippe Moussalli <[email protected]>
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 @mrchtr, I think these are the last ones. I think the tests should pass with these changes.
type: array | ||
items: | ||
type: float32 | ||
additionalFields: false |
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.
This was removed for now, right?
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.
Would leave it here for now. The file is moved to a different folder anyway in #655.
src/fondant/core/manifest.py
Outdated
else: | ||
self._specification["fields"][field.name] = { | ||
"location": f"/{self.component_id}", | ||
"type": field.type.name, |
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.
This broke some of the tests though.
>>> type.to_json()
{
"type": type
}
So now we get:
{
"location": ...,
"type": {
"type": type
}
}
I think we can solve it like this:
self._specification["fields"][field.name] = {
"location": f"/{self.component_id}",
**field.type.name,
}
FYI, as merge strategy, let's squash merge your separate PRs into your feature branch, and then rebase and merge the feature branch when it's ready. Then we keep the PRs as separate commits on main. |
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.
Great work @mrchtr!
06186c1
into
feature/redesign-dataset-format-and-interface
First PR related to the data structure redesign. Implements the following: - New manifest structure (including validation, and evolution) - New ComponentSpec structure (including validation) - Removes `Subsets` and `Index` Not all tests are running successfully. But this are already quite a few changes. Therefore, I've created PR on feature branch `feature/redesign-dataset-format-and-interface`, to have quicker feedback loops. --------- Co-authored-by: Robbe Sneyders <[email protected]> Co-authored-by: Philippe Moussalli <[email protected]>
First PR related to the data structure redesign. Implements the following: - New manifest structure (including validation, and evolution) - New ComponentSpec structure (including validation) - Removes `Subsets` and `Index` Not all tests are running successfully. But this are already quite a few changes. Therefore, I've created PR on feature branch `feature/redesign-dataset-format-and-interface`, to have quicker feedback loops. --------- Co-authored-by: Robbe Sneyders <[email protected]> Co-authored-by: Philippe Moussalli <[email protected]>
First PR related to the data structure redesign.
Implements the following:
Subsets
andIndex
Not all tests are running successfully. But this are already quite a few changes. Therefore, I've created PR on feature branch
feature/redesign-dataset-format-and-interface
, to have quicker feedback loops.