You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are subtle differences between a way that Google Sheets and Excel treats some A1 notation - eg. unbounded ranges. It seems from my perspective that these differences are one of main reasons for current roadblock on some of the open issues, eg: #26#30#35.
As cellranger seems to be mostly focused on providing low-level functionalities for other 📦, I think it could be possible to add some package-wise option for which features should be possible. Function could be used in package .onLoad determining cellranger functions behaviour package-wise.
The text was updated successfully, but these errors were encountered:
There are subtle differences between a way that Google Sheets and Excel treats some A1 notation - eg. unbounded ranges. It seems from my perspective that these differences are one of main reasons for current roadblock on some of the open issues, eg: #26 #30 #35.
As
cellranger
seems to be mostly focused on providing low-level functionalities for other 📦, I think it could be possible to add some package-wise option for which features should be possible. Function could be used in package.onLoad
determiningcellranger
functions behaviour package-wise.The text was updated successfully, but these errors were encountered: