-
Notifications
You must be signed in to change notification settings - Fork 13
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
✨ Add SpatialDataCurator
#2290
✨ Add SpatialDataCurator
#2290
Conversation
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2290 +/- ##
==========================================
- Coverage 92.82% 92.81% -0.02%
==========================================
Files 55 56 +1
Lines 7202 7442 +240
==========================================
+ Hits 6685 6907 +222
- Misses 517 535 +18 ☔ View full report in Codecov by Sentry. |
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
docs job |
We had this many times, it is a |
No I feel almost the entire curator file should be just another repo, it feels so heavy to run all the CI with tiledbsoma and spatialdata and many more in the future if I want to make an unrelated change. I get that Alex is a huge fan of monorepo, but if we continue supporting many 100 more formats, do we really want to run all these CI in every PR push? |
Signed-off-by: zethson <[email protected]>
Sorry for being slow here. My view is that we can't keep adding jobs to the matrix but we should switch to a different model of managing CI. If we keep adding jobs @sunnyosun's concern up there is 100% justified, so we have to something better. Cross-pasting what I suggested on Slack las Monday:
I'll now look through the changes to make suggestions on organizing the code. |
I think we also should eliminate |
Folders
Docs:
New suggested idiom: ln.curators.SpatialDataCurator(...) instead of ln.Curator.from_spatialdata(...) |
…ure/spatialdata_curator
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
…ure/spatialdata_curator
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Signed-off-by: zethson <[email protected]>
Followup in #2303 With the next release we can yank |
Great! :D -- One PyPI package less! |
This PR broke cellxgene-lamin because the import filename was changed from ._curate to curators... |
Sorry - I'll fix that |
I think the cellxgene-lamin package should also disappear and be part of lamindb just like spatial curator |
I'm already doing it! |
|
Also this fix is now gone since this PR: #2299 It's probably due to you deleting the _curator.py file before rebasing... |
Sorryyyy also on me then, yes.. |
sample
)dorny/paths-filter@v3
to condition the groups that are executed. I tested several options and I can only say now that it executes the spatial group but I can't test with this PR the cases where it should NOT execute the spatial group. I'll follow up if necessary.