[ENH]: Prepare Junifer for extension support #366
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!366
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/junifer-ext"
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?
Are you requiring a new dataset or marker?
Which feature do you want to include?
If I install
junilogorjunifer-data, I would like to call them usingjunifer logorjunifer data, through the junifer click group.How do you imagine this integrated in junifer?
1- On importing junifer, we "import and register all extensions"
2- Each extensions provides a "group name" and registers this group under the junifer click group.
Do you have a sample code that implements this outside of junifer?
No response
Anything else to say?
No response
Codecov Report
All modified and coverable lines are covered by tests ✅
Additional details and impacted files
100.00% <ø> (∅)85.74% <100.00%> (∅)Flags with carried forward coverage won't be shown. Click here to find out more.
100.00% <100.00%> (ø)81.81% <ø> (ø)🚀 New features to boost your workflow:
https://juaml.github.io/junifer/pr-preview/pr-366/
Built to branch
gh-pagesat 2025-03-21 14:14 UTC.Preview will be ready when the GitHub Pages deployment is complete.