-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add try-with-resources to annotation processor #45193
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
base: main
Are you sure you want to change the base?
Add try-with-resources to annotation processor #45193
Conversation
API change check API changes are not detected in this pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General question: is there was a particular reason you chose to use try-with-resources in some tests and to explicitly call close()
in others?
// Always close the network response in this situation as converting to a byte[] will read the entire | ||
// response. This should complete the connection, but let's be safe. This must be done after getting the | ||
// byte[] though. | ||
closeResponse(body, "Close the network response as the body should be consumed."); | ||
|
||
// Return responseBodyBytes as-is which will have the behavior of null -> null, empty -> empty, and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit; responseBodyBytes
is not used as a variable any longer.
boolean returnIsResponse = TypeConverter.isResponseType(returnType); | ||
|
||
// TODO (alzimmer): Base64Uri needs to be handled. Determine how this will show up in code generation and then | ||
// add support for it. | ||
if (entityType == Void.TYPE || entityType == Void.class) { | ||
// Return is void, Void, or Response<Void>, close the network response and return null as the value. | ||
if (returnType.getKind() == TypeKind.VOID) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean we only close the response explicitly if the method returns void
? Would we keep it open for Void
or Response<Void>
? Why?
Description
Changes annotation processor to use a try-with-resources block when the
Response<BinaryData>
will be closed. This ensures that if any errors occur before the network response is closed that resources won't be leaked.All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines