[Feature Request]: Remove unneeded dependencies from {teal.transform}

[m7pr]

There is a couple of R packages that could be removed from the package. Below is the list of few. Maybe at least a couple can be removed.

• [Feature Request]: remove {tidyr} from {teal.transform} #189
• [Feature Request]: remove {tidyselect} from {teal.transform} #190
• [Feature Request]: remove {rlang} from {teal.transform} #191
• [Feature Request]: remove {shiny} from {teal.transform} #192
• [Feature Request]: remove {teal.code} from {teal.transform} #193

[m7pr]

CC @donyunardi and @pawelru . Should we do this before or after the initial CRAN release? I think removal of those packages should take a day for the removal, and another one for testing the package. I have no idea how much time would take testing all other packages + deployed teal gallery apps after removal of few packages from the code base of {teal.transform}. Proposing this improvement as I know we are planning to have a thorough review of {teal.gallery} apps anyway.

[donyunardi]

Hi @m7pr
Thanks for this. I'm all for removing unneeded dependencies.
Since this is not a blocker for our initial CRAN release, let's do this after.

[pawelru]

I have spoken with @donyunardi and we agreed to take a minimalist approach to release "as is". These are all good discoveries and I really don't want to discourage you but my concern here is that such things will prolong the release cycle and there are teal.modules.xyz waiting on the list.

The other thing is that I do have some idea about a fundamental package refactor in which rlang, shiny and teal.code play key role. I don't mind the rest.

[m7pr]

Thanks @pawelru and @donyunardi for the reply. I totally understand this is not critical and can extend the release period. Let's talk once we get back to the actual refactor, after all {teal.*} packages are on CRAN!