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
If the quantifier pool size is near the minimum required quantifier pool size, you can't predict if there will be enough quantifiers, because you don't know the composition of the praise bins. Additionally there are many different ways for the bins to be packed (and some intentional randomness), and thus assignQuantifiersDryRun() doesn't know if there will be enough quantifiers for the bins until it generates the bins.
This presents a UX issue, because a user may see "quantifier pool requirements are met" then have a quantification assignment fail.
Overview
The user calls verifyQuantiferPoolSize(), which calls assignQuantifiersDryRun() once.
Then the user calls assignQuantifiers() which calls assignQuantifiersDryRun() again.
It is possible for the quantifier pool to be sufficient for the first run's bin-packing arrangement, but not for the second run's different bin-packing arrangement.
Options to Resolve
Modify the architecture verifyQuantiferPoolSize() and assignQuantifiers() to act like a multi-part form, where the form state is saved between steps
Modify verifyQuantiferPoolSize() & AssignDialog component UX to indicate it is only capable of providing an estimate of the number of quantifiers needed. Do not actually run assignQuantifiersDryRun() within verifyQuantiferPoolSize()
The text was updated successfully, but these errors were encountered:
If the quantifier pool size is near the minimum required quantifier pool size, you can't predict if there will be enough quantifiers, because you don't know the composition of the praise bins. Additionally there are many different ways for the bins to be packed (and some intentional randomness), and thus
assignQuantifiersDryRun()
doesn't know if there will be enough quantifiers for the bins until it generates the bins.This presents a UX issue, because a user may see "quantifier pool requirements are met" then have a quantification assignment fail.
Overview
verifyQuantiferPoolSize()
, which callsassignQuantifiersDryRun()
once.assignQuantifiers()
which callsassignQuantifiersDryRun()
again.Options to Resolve
verifyQuantiferPoolSize()
andassignQuantifiers()
to act like a multi-part form, where the form state is saved between stepsverifyQuantiferPoolSize()
&AssignDialog
component UX to indicate it is only capable of providing an estimate of the number of quantifiers needed. Do not actually runassignQuantifiersDryRun()
withinverifyQuantiferPoolSize()
The text was updated successfully, but these errors were encountered: