Closed gogonzo closed 7 months ago
The examples were accepted in teal.code
. Is this because that was not the initial submission? If so, I take it the exmaples will be added back in the next release? Perhaps 0.4.1
?
It might depend on a reviewer also.
perhaps 0.4.1
Yup, let's do this. But Today we can maybe move it to @details for a while - I'm waiting for opinion from CRAN reviewer.
Do you think they could waive the restriction if we explain that these are dev-oriented examples?
Do you think they could waive the restriction if we explain that these are dev-oriented examples?
I've tried explain this before with other package, I guess it was teal.code initial submission. I can't remember now and email has limited history also.
Do you want to pre-emptively prepare that move to @details
?
I can do it quickly right now and target the release-candidate-v0.4.0
branch
Do you want to pre-emptively prepare that move to @details ?
Let's wait for answer from CRAN about this. We can address other comments first and wait for their opinion. I'll do respective changes over the weekend if answer comes too late 👍
ok :crossed_fingers:
I'm curious about the rationale behind allowing documentation, but not examples. I can only think that they don't want to waste resources running these examples given that they have to test 10k+ packages regularly on multiple platforms
Still, it seems like they are promoting poor development practices by preventing better documentation
Probably those examples wouldn't run if we hadn't done the getFromNamespace
trick. It makes me think it was an automated process: compare names of functions in examples against names of exported funcitons.
But then why would it be allowed in teal.code
? :thinking:
We don't have any references describing the methods on teal.data
so as far as I can tell there are only 2 actions required for resubmission
DESCRIPTION
file
@examples
If they don't allow examples in the way we have them today, we can resubmit them in another CRAN release, as the next one does not have a human verification. We can do it even after a day or the first CRAN release.
If they don't allow examples in the way we have them today, we can resubmit them in another CRAN release, as the next one does not have a human verification. We can do it even after a day or the first CRAN release.
Good point. We can remove the examples IN ONE COMMIT and revert this commit easily later. We just need to keep the merged branch longer to preserver the commit (commits are squashed when merged to main). This is the fastest solution. Examples are just for us so we can address this later. So I suggest to remove examples now
What exactly are the private examples here? I can't find any on teal.data
This?
Examples for unexported function default_cdisc_join_keys() in: col_labels.Rd
Examples for unexported function default_cdisc_join_keys() in: col_labels.Rd
In col_labels.Rd
all the calls/expressions on @examples
are all to exported functions (col_labels<-
, col_labels
, col_relabel
, get_labels
)
default_cdisc_join_keys
is exported (but not a function nor does it have @examples
)
And the only getFromNamespace
hit is when we import lang2calls
(R/zzz.R
)
let's submit without the change in examples then haha
Comments from CRAN reviewer.