🎨 Let Curator.validate()
throw an error
#2417
Merged
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.
Is part of a sequence of PRs that refactors the curators:
AnnDataCurator
#2418BaseCurator
asCurator
and introduceCatCurator
#2416organism
handling in curators #2415CatCurator
#2413CellxGene
schema #2412PertCurator
fromwetlab
here and addCellxGene
Curator
test #2408CellxGene
Curator
fromcellxgene-lamin
here #2403DataFrameCurator
#2388The new-style curators are now consistent with pydantic and pandera in that they raise informative errors upon
.validate()
rather than returningFalse
.Say, there is a typo in the "T cell" label:
Or a column is missing from a
DataFrame
(viapandera
under-the-hood):The old-style family of
CatCurator
classes keeps returning a boolean upon.validate()
for backward compatibility.Also:
lamindb.core.exceptions
got moved tolamindb.errors
.See internal Slack thread.