-
Notifications
You must be signed in to change notification settings - Fork 6
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
Zone picking list zones on start #89
Zone picking list zones on start #89
Conversation
Codecov Report
@@ Coverage Diff @@
## 13.0-shopfloor #89 +/- ##
==================================================
+ Coverage 91.06% 92.69% +1.63%
==================================================
Files 55 55
Lines 3972 4027 +55
==================================================
+ Hits 3617 3733 +116
+ Misses 355 294 -61
Continue to review full report at Codecov.
|
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.
One question and one comment
e4fd1fa
to
4ea79fc
Compare
4ea79fc
to
504b290
Compare
'start' is an alias for the initial state. If we load that at init we must pick initial state data from the right key. The key could be 'start' or the real state name. Better to use always the next_state key to access data from the server.
When the operator starts with zone picking scenario the 1st screen presents the list of zones that have lines to process.
504b290
to
390b1a4
Compare
TODO
ref: 1434