Unexpected split of generic arguments

[boris-petrov]

Prettier-Java 2.7.3

Playground link

--print-width 100

Input:

public abstract class Foo implements MyInterface {
	@Override
	public String foo() {
		Map<String, Map<String, Object>> deepCopy =
			(Map<String, Map<String, Object>>) Helpers.deepCopyOf(map);
	}
}

Output:

public abstract class Foo implements MyInterface {

	@Override
	public String foo() {
		Map<String, Map<String, Object>> deepCopy = (Map<
			String,
			Map<String, Object>
		>) Helpers.deepCopyOf(map);
	}
}

Expected behavior:
I don't expect the generic arguments to be split like this. It's better if the method-call is on a new line instead.

[csemrau]

Just noticed the same problem, with a simple <?> wildcard.

Prettier-java 2.7.6, with a printWidth 140, formats like this:

class TestWildcards {

    static class SortOrderForReference {}

    interface ConstraintFactory<T> {}

    static class ReferenceConstraintFactory<T> implements ConstraintFactory<T> {

        SortOrderForReference sortOrderForReference;
    }

    static class AttributeDef {

        ConstraintFactory<?> constraintFactory;
    }

    private void test(AttributeDef attributeDef) {
        // single line is just within the print width (140)
        SortOrderForReference sortOrderForRefA1234 = ((ReferenceConstraintFactory<?>) attributeDef.constraintFactory).sortOrderForReference;
        // single line would be longer than the print width
        SortOrderForReference sortOrderForRefB12345 = ((ReferenceConstraintFactory<
                ?
            >) attributeDef.constraintFactory).sortOrderForReference;
    }
}

Prettier 2.6.8 formats the method like this, which is what I'd expect here:

    private void test(AttributeDef attributeDef) {
        // single line is within the print width (140)
        SortOrderForReference sortOrderForRefA1234 = ((ReferenceConstraintFactory<?>) attributeDef.constraintFactory).sortOrderForReference;
        // single line would be longer than the print width
        SortOrderForReference sortOrderForRefB12345 =
            ((ReferenceConstraintFactory<?>) attributeDef.constraintFactory).sortOrderForReference;
    }

By using classes and fields of different name length, the scenario can be adapted to different print widths.