[ENH]: Simplify Storage interface #472
No reviewers
Labels
No labels
CRITICAL
Stale
WIP
bug
concept
coordinate
dataset
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
maintenance
maps
marker
mask
on hold
parcellation
preprocess
question
ready
storage
template-space
triage
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
juaml/junifer!472
Loading…
Reference in a new issue
No description provided.
Delete branch "refactor/storage"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR refactors the
Storageinterface to simplify implementation logic and update typing annotations.Codecov Report
✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.64%. Comparing base (
6eb4899) to head (eca0f41).⚠️ Report is 25 commits behind head on main.
Additional details and impacted files
100.00% <ø> (ø)Flags with carried forward coverage won't be shown. Click here to find out more.
80.35% <ø> (+3.88%)93.60% <ø> (-0.43%)95.12% <ø> (-0.63%)96.07% <ø> (-0.36%)94.87% <ø> (+2.10%)🚀 New features to boost your workflow:
CI passes on juseless.
What about the timeseries 2d?
What about a remote URI like in the SQLite case? Is this still a "Path"?
This was set downstream because an URI can be anything, not only a path.
SQLiteFeatureStorage doesn't support timeseries_2d.
Implementations of SQLite and HDF5 feature storage both need to point to a file which can be expressed as a Path. I don't understand what you mean by "remote URI", an example might help.
It was thought to work with remote SQL databases too. SQLite was just an implementation of the SQL interface. Though for the moment, might be ok to keep it like this.