Expose all answers in Result

[airibarne]

Hi @12rambau! Firstly, thank you for your contribution, excellent and very needed package within the Copier ecosystem 😄

Description

In my templates, I normally have hidden answers I use as computed values, e.g. a repo name derived from a project name by eliminating spaces and lowercasing. For that, I use the when: false pattern as described here.

Now, to properly write tests for my templates, I'd like to have access to that hidden values. With the current implementation, I cannot, since the Result class holds only the output of Worker._answers_to_remember(), which only contains those unhidden answers.

Solution

I'd like to have access to another attribute in the Result class that contains, maybe, the output of Worker.answers.user, or even the whole Worker.answers's copier.AnswersMap object.

Alternatives

I cannot figure out an alternative with the current implementation.

Extra context

I can make a PR, if you have some opinion on which object should we hold in the Result class, as long as you find the feature useful.

[gabrielbdornas]

Hello @12rambau, as @airibarne said, nice work. Congratulation!

Is there any news about this feature suggestion? I really think it could be a great improvement for the project.

[12rambau]

I'm lacking OSS time but I can definitely review a PR. On my side I'm not using the "hidden" answers I simply precompute value that the user can overwrite if needed: https://github.com/12rambau/pypackage/blob/main/copier.yaml

[looztra]

I could definitely work on this one as I would also like to be able to get access to these private answers.

How do you see that @12rambau @airibarne @gabrielbdornas ?:

• keep the current contract for answers and add another answers_full (or something like that) property that also includes the private answers
• change the current contract for answers and return all answers?
• something else

[12rambau]

HI @looztra If you're still willing to offer a PR I think the best way to move forward is to add a full_answers to not break the current implementation for downstream users.