Skip to content

[http client] Use more generic Type rather than ParameterizedType #194

New issue

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

Merged
merged 3 commits into from
Apr 3, 2023

Conversation

SentryMan
Copy link
Collaborator

Hmm, I'm thinking it would be good if we loosen the restriction from only parameterized types.

@rbygrave rbygrave changed the title use more generic type [http client] Use more generic Type rather than ParameterizedType Apr 3, 2023
@@ -75,15 +75,15 @@ public HttpException(int statusCode, Throwable cause) {
}

HttpException(HttpResponse<?> httpResponse, DHttpClientContext context) {
super();
super("Http Call failed with status: " + httpResponse.statusCode());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'll change that to "Http call ..." using lower case "c" for "call" as we have HttpCall as a type

@rbygrave rbygrave added this to the 1.35 milestone Apr 3, 2023
@rbygrave rbygrave merged commit 208b58d into avaje:master Apr 3, 2023
@SentryMan SentryMan deleted the types branch April 3, 2023 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants