Github user zero323 commented on a diff in the pull request:

    https://github.com/apache/spark/pull/17825#discussion_r115085302
  
    --- Diff: R/pkg/R/generics.R ---
    @@ -387,6 +387,16 @@ setGeneric("value", function(bcast) { 
standardGeneric("value") })
     #' @export
     setGeneric("agg", function (x, ...) { standardGeneric("agg") })
     
    +#' alias
    +#'
    +#' Set a new name for a Column or a SparkDataFrame. Equivalent to SQL "AS" 
keyword.
    +#'
    +#' @name alias
    +#' @rdname alias
    +#' @param object x a Column or a SparkDataFrame
    +#' @param data new name to use
    --- End diff --
    
    On the bright side it looks like matching `@rdname` and `@aliases` like:
    
    ```r
    #' alias
    #'
    #' @aliases alias,SparkDataFrame-method
    #' @family SparkDataFrame functions
    #' @rdname alias,SparkDataFrame-method
    #' @name alias
    ...
    ```
    and
    
    ```r
    #' alias
    #'
    #' @aliases alias,SparkDataFrame-method
    #' @family SparkDataFrame functions
    #' @rdname alias,SparkDataFrame-method
    #' @name alias
    ...
    ```
    (I hope this is what you mean) indeed solves SPARK-18825. But it doesn't 
generate any docs for these two and makes CRAN checker unhappy:
    
    ```
    Undocumented S4 methods:
      generic 'alias' and siglist 'Column'
      generic 'alias' and siglist 'SparkDataFrame'
    ```
    Docs for generic are created but it doesn't help us here. Even if we bring 
`@examples` there we still have to deal with CRAN.
    
    Theres is also my favorite `\name must exist and be unique in Rd files` 
which doesn't gives us much room here, does it?
    
    I opened to suggestions, but personally I am out ideas. I've been digging 
trough `roxygen` docs, but between CRAN,  S4 requirements, `roxygen` limitation 
and our own rules there is not much room left.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to