Hello - I ran into this issue with a seurat object that has a UMAP that was created with an alternate key property. If this happens, the colnames of the embeddings would be something like 'rnaUMAP_1', not UMAP_1. This is a simple fix for that situation.
@wu-yc: the second commits switch from needing to use library() in the module to importing it in NAMESPACE. I think that's going to be more robust, including if another package loads this.
Hello - I ran into this issue with a seurat object that has a UMAP that was created with an alternate key property. If this happens, the colnames of the embeddings would be something like 'rnaUMAP_1', not UMAP_1. This is a simple fix for that situation.