Repository navigation
feat: printed labels create open orders that take their items from the first seal - #25
Merged
Merged
Conversation
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.
Printing a label now calls POST /orders, so the station can bind the scanned QR and the label shows up as an order instead of 404ing as "No order ... in the system". A label printed without items is an open order: YOLOE watches a broad everyday vocabulary and the first seal writes what it tracked as the order's items.
This sat unmerged on a local branch; the rehearsal ran from it and the demo ran from main without it. The API half is already deployed on the VM (byte-identical), so no deploy-api is needed.
just checkpasses.