-
Notifications
You must be signed in to change notification settings - Fork 25
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
CIRC-2051 Add ecsRequestRouting parameter to allowed-service-points #1451
base: master
Are you sure you want to change the base?
Conversation
@@ -99,6 +100,13 @@ private static Result<AllowedServicePointsRequest> buildRequest(RoutingContext r | |||
useStubItem); | |||
errors.add(String.format("useStubItem is not a valid boolean: %s.", useStubItem)); | |||
} | |||
if (ecsRequestRouting != null && !"true".equals(ecsRequestRouting) |
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.
Since we are validating boolean string twice now, do you think this check deserves a separate method? Something like isIvalidBooleanString(String boolean)
? "ecsRequestRouting" | ||
: "pickupLocation"; |
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.
So we are now searching either by ecsRequestRouting
or pickupLocation
. Do we not care about the value of pickupLocation
when fetching ECS routing service points?
9b43fb0
to
b67fbb5
Compare
Quality Gate passedIssues Measures |
Purpose
Add a non-required boolean parameter ecsRequestRouting to an endpoint GET /circulation/requests/allowed-service-points. Default value is false.
When set to true, it should change the behavior:
Instead of returning service points with pickupLocation=true we need to only return service points with ecsRequestRouting=true
Resolves: CIRC-2051