-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix response status if not found (#39) #40
Conversation
Signed-off-by: yichen88 <[email protected]>
if (status == Response.Status.OK) { | ||
return Optional.of(readEntityAndLog(response, entityType)); | ||
} else if (status == Response.Status.NO_CONTENT) { | ||
if (status == Response.Status.NO_CONTENT || status == Response.Status.NOT_FOUND) { | ||
LOGGER.trace(" --> null"); | ||
return Optional.empty(); |
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.
Why do you remove the INTERNAL_SERVER_ERROR case ?
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.
and the UnexpectedResponse case ?
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.
these cases are still checked in readEntityIfOk()
.
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.
Ah yes sorry, didn't see it.
if (status == Response.Status.OK) { | ||
return Optional.of(readEntityAndLog(response, entityType)); | ||
} else if (status == Response.Status.NO_CONTENT) { | ||
if (status == Response.Status.NO_CONTENT || status == Response.Status.NOT_FOUND) { |
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.
Maybe add a comment that the NO_CONTENT is for backwards compatibility with afs-server < version XX
Kudos, SonarCloud Quality Gate passed! 0 Bugs |
Signed-off-by: yichen88 <[email protected]>
eeb6745
to
62f3203
Compare
Thanks, sorry for the delay ! |
Kudos, SonarCloud Quality Gate passed! 0 Bugs 100.0% Coverage The version of Java (1.8.0_252) you have used to run this analysis is deprecated and we will stop accepting it from October 2020. Please update to at least Java 11. |
Signed-off-by: yichen88 [email protected]
Please check if the PR fulfills these requirements (please use
'[x]'
to check the checkboxes, or submit the PR and then click the checkboxes)Does this PR already have an issue describing the problem ? If so, link to this issue using
'#XXX'
and skip the rest#39
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API? If yes, check the following:
Other information:
(if any of the questions/checkboxes don't apply, please delete them entirely)