You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although it is technically possible to have a "no advance" situation (error) and then some other play, allowing it would raise an undefined number of clashing situation that would require separate validations.
Eg.:
Also it is not possible to have "no advance" at they some play at 2nd base, only at 3rd:
For now the solution is to disable this completely. We may think of white-listing certain combinations if they prove necessary later.
update GUI components to disallow selecting extra input after "no advance" situation
check list of "NoAdvanceSituations" in wbsc-validation.ts
add info in "Limitations" section
update checkNoAdvances validation comment
The text was updated successfully, but these errors were encountered:
It works in
v1.1
, was not covered via #217 yet.Although it is technically possible to have a "no advance" situation (error) and then some other play, allowing it would raise an undefined number of clashing situation that would require separate validations.
Eg.:
Also it is not possible to have "no advance" at they some play at 2nd base, only at 3rd:
For now the solution is to disable this completely. We may think of white-listing certain combinations if they prove necessary later.
add info in "Limitations" sectionThe text was updated successfully, but these errors were encountered: