Add list-all orders endpoint for the admin orders view#99
Closed
CarsonL15 wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Consolidating into the Sprint 3 PR instead — both pipelines still trigger by path filter on merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an admin-facing "list all orders" capability to the Order Service so the Admin & Maintenance App can show every order (issue #53). Today
GET /api/ordersrequires acustomerId; an admin has no way to list orders across customers.Change
GET /api/orders—customerIdis now optional:Backward compatible: the customer web app's existing
?customerId=calls behave exactly as before.OrdersController.GetOrdersbranches on whethercustomerIdis suppliedIOrderService.GetAllOrdersAsync+ implementation (noWHERE CustomerIdfilter)Relates to #53 (consumed by the admin Orders view).