Remembering prompts between requests

[MichaelXavier]

Did you search for existing issues already?
Yes

Is your feature request related to a problem? Please describe.
I make use of the prompt() function for pieces of my recipes that may vary, which is especially important because I commit my slumber file to source control. I tend to hit the same recipe multiple times while testing and it gets pretty tedious to have to keep filling in the same value in the prompt. When I have multiple prompts I usually have to have a scratch pad open and keep copying and pasting the prompts.

Describe the solution you'd like
I don't know if the persistence system or if there's any concept of a session when you start slumber but I would like prompts with a given message to default to the last value entered for that prompt, or at least to be configurable to do so. Ideally this would key on the message and span the entire collection so e.g. a prompt for Order Id would be pre-filled across multiple recipes. If it could just apply to a single recipe that would still be a big improvement.

Describe alternatives you've considered
I've also tried pushing the prompt into profile data but it still prompts every time with no defaulting.

Additional context
None

[LucasPickering]

Thanks for the suggestion. FWIW prompt() supports a default keyword arg, which would allow you to statically set a default like so:

url: "{{ host }}/users/{{ prompt(message='User ID', default=1) }}"

You could of course pass any expression to default=, e.g. it could read from a file or response.

But I've definitely been in this same situation myself, where I'm running a request repeatedly and keep having to enter the same value over and over. It doesn't always make sense to put the default in the collection file. So I like your suggestion of persisting the previous value as a default. The hard part is figuring out how to link prompt() calls between requests. Your suggestion of using the message is possible, but I don't love the idea of treating a display string as unique and stable. Another option is to add an id= parameter that would be unique+stable, but that is clunky and I don't think it would get much use. It may be possible to identity the prompt() calls by their source position, but that'll take some investigation.

I'll leave this open for now, but hopefully the default= param does what you need for now.

[MichaelXavier]

I think defaulting is a decent workaround for now. I can just make sure not to commit those changes. Thanks for the consideration!