Closed donaldcampbelljr closed 3 months ago
We currently have the field definition as a list[dict]
:
It does show up during model generation:
Ok, I think there might be something else going on here. If I remove the collection of images from my test and the recursive schema, I get the same error but for the next complex object, e.g output_file
.
Oh, its our check to determine if the dependencies are satisfied. It creates an initial table using a different schema than the test:
pipestat report --c 'tests/data/config.yaml' -i 'name_of_something' -v 'test_value' -r 'dependency_value'"
So, this causes issues with the very first test IF you are running them individually (and the schema in the test is not the same as the dependency test). I actually ran into this issue last week and did not realize/remember I had reverted the checks back to their original state.
I think my changing of the default schema in the testing config will alleviate this problem for now: https://github.com/pepkit/pipestat/commit/b13299f593df4caaab02b5cfc20fdb36d413964e
Using a complex output schema:
and attempting to report a value:
I see an error during testing:
Double checking the db, it appears that column is indeed not being created during table creation.