Description Markus Keller 2014-01-15 13:48:04 EST

Javadoc hover/view: Improve header rendering for monster methods with a huge signature.

Example:

In java.lang.reflect.AnnotatedElement#getDeclaredAnnotationsByType(Class<T>), show Javadoc for the invocation of Collectors.toMap(...).

The hover shows a breathtaking header:

<Annotation, Class<? extends Annotation>, Object, Map<Class<? extends Annotation>, Object>> Collector<Annotation, ?, Map<Class<? extends Annotation>, Object>> java.util.stream.Collectors.toMap(Function<? super Annotation, ? extends Class<? extends Annotation>> keyMapper, Function<? super Annotation, ? extends Object> valueMapper, BinaryOperator<Object> mergeFunction, Supplier<Map<Class<? extends Annotation>, Object>> mapSupplier)

For method headers of a certain length ( > 2 lines?), we should switch to a format like this, where line breaks and indentation help identify the structure:

<Annotation, Class<? extends Annotation>, Object, Map<Class<? extends Annotation>, Object>>
Collector<Annotation, ?, Map<Class<? extends Annotation>, Object>> java.util.stream.Collectors.toMap(
    Function<? super Annotation, ? extends Class<? extends Annotation>> keyMapper,
    Function<? super Annotation, ? extends Object> valueMapper,
    BinaryOperator<Object> mergeFunction,
    Supplier<Map<Class<? extends Annotation>, Object>> mapSupplier)

The implementation in JavaElementLinkedLabelComposer could use a special FlexibleBuffer that records positions for optional "<br>" and "<br>\t", and then decides in toString() whether to insert the optional formatting or not.

We should also check how it looks if we render types non-bold. Or maybe all types except those in the method name qualifier.