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
The case
After answering a confirm type question, third values have to be conditionally calculated and get saved to a (generator's config) file. Some of these values, later on, will also be used as defaults to some other questions.
The problem
Third value calculations and their storage cannot be done right after the answer of the questions but later on.
Some third value calculations have to be done in the next questions in 'default' property which is not the ideal place and at the same time to get stored in the config file since they are ready.
The remaining values have to be calculated and get stored in the promise part.
So, there are two different places from which calculations and storage take place.
Potential solution
A new function property (eg action) could be added as a degree of freedom. User would decide in which part - question object or promise (then()) - additional tasks will be written. For example, tasks that require different answers are written in the promise part but tasks based only on a question input could be written in the action property.
Note: In other types where filter is available, local tasks "smartly & abusively" take place through its function which finally just returns the input unchanged; a solution not so elegant. So, imho, a separate function property for individual tasks based on single input would be a nice feature which does not break backward compatibility, too.
Tia
The text was updated successfully, but these errors were encountered:
The case
After answering a confirm type question, third values have to be conditionally calculated and get saved to a (generator's config) file. Some of these values, later on, will also be used as defaults to some other questions.
The problem
Potential solution
A new function property (eg
action
) could be added as a degree of freedom. User would decide in which part - question object or promise (then()
) - additional tasks will be written. For example, tasks that require different answers are written in the promise part but tasks based only on a question input could be written in theaction
property.Note: In other types where
filter
is available, local tasks "smartly & abusively" take place through its function which finally just returns the input unchanged; a solution not so elegant. So, imho, a separate function property for individual tasks based on single input would be a nice feature which does not break backward compatibility, too.Tia
The text was updated successfully, but these errors were encountered: