Closed TeemuStenhammar closed 7 years ago
It seems it does not have to be anonymous class at all as the following test case shows the same bahavior:
static class Actual extends Container<String> {
}
@Test
public void shouldFindFieldOfTypeStringFromActual() {
Actual actual = new Actual();
ResolvedType strType = typeResolver.resolve(String.class);
ResolvedType fieldType = getFirstFieldType(actual.getClass());
assertEquals(strType.getSignature(), fieldType.getSignature());
}
Could be related to #33, #28? Does this occur with 1.3.3 too (which has fixes for both earlier issues)
Those two were manifestations of the same issue. Sorry, I totally missed that you had released a new version and looked only for open issues to find similar one. Now my tests are all green again. Thanks!
@TeemuStenhammar np. Just glad it wasn't a new thing. It's bit of a concern still, but at least your case did not expose new unhandled case.
Hi,
I ran into a mysterious behavior, for me at least. Consider the following two test cases:
The anonymous version states that the type of the field is
while non-anonymous gives correct plain String. Is this a known thing that happens with anonymous classes or what is going on?