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
You can also finish the first generation, commit everything, then run copier update, change your answer for this question and amend the previous commit.
You can also finish the first generation, commit everything, then run copier update, change your answer for this question and amend the previous commit.
While this is a working idea, it will not recreate dynamic "look-behind" defaults.
For instance, if an answer foo has a default of {{previous_answer}}, then in copier update it's not re-rendered from the newly answered previous_answer value, but the old foo value is used. This might be quite inconvenient in questionnaires where there are quite a few questions defaults of which depend on the previous ones (which is my case).
You can also finish the first generation, commit everything, then run copier update, change your answer for this question and amend the previous commit.
Another issue with this is if you have _tasks scripts to run after template instantiation, then it will run them using incorrect values first before getting a chance to change the response.
Actual Situation
Assuming I make a mistake when answering the last question, I have to Ctrl+C and answer everything again.
Desired Situation
I can press Ctrl+Z to get back to previous question and correct it.
Proposed solution
I'll let you know when I have a concrete idea worth sharing.
The text was updated successfully, but these errors were encountered: