Accessing the internal API for CRAN package

[JanMarvin]

Hi @rich-iannone , hi @olivroy ,

it happens to be that I spun up a small package to write gt objects to openxlsx2 worksheets. Even though I’m not even a gt user, at least not yet.

My package works quite well, as far as I could test, and even though it wasn’t my initial intention, I was asked if it would be submitted to CRAN. And here my headache starts :)

To avoid duplicating much of gt, I use a single entry to gt here:

https://github.com/JanMarvin/gtxlsx/blob/dffd0d9a9380a0ac26bc55f9b7f141d7ff5b6036/R/utils.R#L14

Via your internal API and, well, the question is are you fine with that? And with fine I mean, if CRAN asks me, if I asked you for permission, could I submit your approval? And this is an open question. If you don’t want this, I won’t pursue this idea any further.

And as maintainer I know the consequences. Your internal API would somehow get public and any changes on your side could cause revdep failures and bureaucracy on your end. And it won’t end with me, even if I avoid all checks and examples on CRAN, if others would use gtxlsx that’s nothing I could influence.

I’ve checked the package API is stable for some years now. Therefore, I see a slim chance that this won’t cause any issues. But it’s your package, your code, and thus your call.

If you have any other suggestions, please let me know.

Best regards,
Marvin

https://github.com/JanMarvin/gtxlsx

[JanMarvin]

Hi, I know this is a bit unusual, but have you had a chance to consider it?

[rich-iannone]

Very sorry for the delay here, but I think this is fine!

[JanMarvin]

Thanks!