You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Mikko Värri (Jira)" <ji...@apache.org> on 2020/05/06 08:48:00 UTC
[jira] [Commented] (GROOVY-9543) groovydoc multiple issues with
generics
[ https://issues.apache.org/jira/browse/GROOVY-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100593#comment-17100593 ]
Mikko Värri commented on GROOVY-9543:
-------------------------------------
Pull request available: [https://github.com/apache/groovy/pull/1239]
> groovydoc multiple issues with generics
> ---------------------------------------
>
> Key: GROOVY-9543
> URL: https://issues.apache.org/jira/browse/GROOVY-9543
> Project: Groovy
> Issue Type: Bug
> Components: GroovyDoc
> Reporter: Mikko Värri
> Priority: Major
> Labels: pull-request-available
> Attachments: class-type-param-doc-issue.png, groovy-method-type-param-issue.png, groovy-title-issue.png, java-title-issue.png, java-type-param-issue.png, method-type-param-doc-issue.png
>
>
> The HTML output of groovydoc doesn't handle generics very well.
> # For Java code, the angle brackets are not shown in the title
> !java-title-issue.png!
> # For Groovy code, any type param bounds are dropped from the title
> !groovy-title-issue.png!
> # For both Java and Groovy, angle brackets in class type param docs ({{@param <A> Blah.}}) are not escaped
> !class-type-param-doc-issue.png!
> and same for method type param docs
> !method-type-param-doc-issue.png!
> # For Java code, method type params are not shown (they are shown for Groovy code)
> !java-type-param-issue.png!
> # For Groovy code, method params and return types show raw types, even though it shows method type params, which makes it confusing
> !groovy-method-type-param-issue.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)