-
Notifications
You must be signed in to change notification settings - Fork 25
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
[python] Enumerations-API refinement #1755
Conversation
4edc807
to
99652a8
Compare
Codecov ReportAttention: ❗ Your organization needs to install the Codecov GitHub app to enable full functionality.
... and 75 files with indirect coverage changes 📢 Thoughts on this report? Let us know!. |
a8a7d88
to
82494b3
Compare
|
e1fb7aa
to
79d94c7
Compare
There is actually two more corrections I need to do. I already solved one. If there are no new enumeration values, then do not evolve the schema (before, we were extending with an empty list). But there's one more issue having to do with Boolean enums. |
408c349
to
08fc2bf
Compare
* This was a problem with a local build where TileDB-Py was built with a different version of core than libtiledbsoma, causing the reader and writer to enter different libtiledb codepaths
08fc2bf
to
47aa7f6
Compare
* Force exporting v3 assays with SeuratObject v5 installed SeuratObject v5 creates v5 assays by default (didn't always). This PR sets options in `SOMAExperimentAxisQuery$to_seurat()` and `SOMAExperimentAxisQuery$to_seurat_assay()` to force SeuratObject to create v3 assays instead of v5 ones Addresses chanzuckerberg/cellxgene-census#816 * Add tests to ensure v3 assays are exported even if v5 is installed * Update tests to not name `slot` in `GetAssayData()` * Don't name `slot` in `SetAssayData()` * Don't name `slot` in `GetAssayData()` * Temporarily stop using `expect_no_condition()` due to bug in SeuratObject
* [c++/python] Depends on core 2.17.3 and TileDB-Py 0.23.2 * Point at dev tiledb-r from #1835
1cce1f5
to
1a3a500
Compare
* Add unit test where subsequent write introduces new category value * Only Extend If New Values Found, Add New Values in Order
* Add unit test where subsequent write introduces new category value * Only Extend If New Values Found, Add New Values in Order Co-authored-by: nguyenv <[email protected]>
Issue and/or context:
#1746
Changes:
DataFrame.create
extend_enumeration
, test creating empty enumeration TileDB-Inc/TileDB-Py#1847; passing locally when built against this branch