We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Things that make one cry:
@Test void thisWorks() { class Foo { Type getType() { return new GenericType<List<String>>() {}.getType(); } } assertThat (new Foo().getType()).isNotNull(); } @Test void thisDoesNot() { class Foo<T> { Type getType() { return new GenericType<List<String>>() {}.getType(); } } assertThat (new Foo<>().getType()).isNotNull(); }
This seems to be a bug in geantryref.
The text was updated successfully, but these errors were encountered:
similar code with geantryref classes works fine:
public void testWorks() { class Foo { Type getType() { return new TypeToken<List<String>>() {}.getType(); } } assertNotNull(new Foo().getType()); } public void testDoesNotWork() { class Foo<T> { Type getType() { return new TypeToken<List<String>>() {}.getType(); } } assertNotNull(new Foo<>().getType()); }
This is some quirk in the GenericTypes implementation which is different from what is in geantryref.
Sorry, something went wrong.
Fix GenericType resolution in parameterized classes
a53d152
Port the code from geantryref.TypeToken#extractType for classes passed into GenericType. Fixes jdbi#2305
Successfully merging a pull request may close this issue.
Things that make one cry:
This seems to be a bug in geantryref.
The text was updated successfully, but these errors were encountered: