chore(release): bump to v1.0.25 - #89
Merged
Merged
Conversation
Ships #87: kitchen-ticket routing walks the nested item tree, so a bundle component whose kitchen differs from its parent's reaches its own kitchen instead of no kitchen at all. Deliberately released AHEAD of backend PR #237, which is what makes OrderDto.Items root-only and is still on backend `develop`. The fix is backward compatible: against today's production backend the printer feed returns SideItems: null on every order, so every line is a root with its own KitchenType and the filter reduces to exactly the old top-level `Where(KitchenType == kitchen)` — byte-identical receipts. The new nested layout only appears once the backend release lands, by which time the client workstations will already have auto-updated. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
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
1 participant
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
ApplicationDisplayVersion,ApplicationVersion24→25,Version) ahead of thedevelop→mainrelease PR.Type
choreWhy release ahead of the backend
Backend PR piwas-21/restaurant-app-backend#237 — which makes
OrderDto.Itemsroot-only — is on backenddevelop, notmain, so the bug is not live yet. Shipping the printer-app first gives the client workstations time to auto-update before the backend flips.The fix is backward compatible: against today's production backend the printer feed returns
SideItems: nullon every order (that was the defect #237 fixed), so every line is a root carrying its ownKitchenType, andKitchenTicketFilterreduces to exactly the old top-levelWhere(KitchenType == kitchen)— byte-identical receipts. The new nested layout only appears once the backend release lands.NFR triage
Standard checklist
develop; targetsdevelopRelease notes