Pull or push `.obsm` or `.varm` annotations.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 134
- Forks
- 23
- Avg merge
- 27m
- Merged PRs (30d)
- 7
Description
Thank you for this amazing package!
Is your feature request related to a problem? Please describe.
Currently, there does not seem to be a build-in method to pull or push obsm or varm anntoations from local tables to the global table.
Describe the solution you'd like
Given that the v3 rc can do this for .obs and .var annotations, I suppose obsm or varm annotations could be moved using the same logic. This would be very convenient!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by comparing the v3 RC pull and push logic for .obs and .var annotations with the requested .obsm and .varm behavior; the work is done when those annotations can be moved between local tables and the global table using equivalent logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100