I just got updated to v6.0 and my prompts with default values have stopped prompting.
๐ Thanks for opening your first issue! If you're reporting a ๐ bug, please make sure
you include steps to reproduce it. If you're requesting a feature ๐, please provide real
use cases that would benefit. ๐ช
To help make this a smooth process, please be sure you have first read the
contributing guidelines.
Update, after playing around a little the behavior is a little more nuanced
The actual behavior I'm seeing is a sort of "caching" experience
I also see the caching behavior if I switch environments
Chiming in because I have this exact same issue, which has rendered the 'prompt' template tag useless for _prompt-once_ scenarios.
This behavior started with the 6.0 update.
Will be fixing this soon
Any update on this? I'm really excited to have this back :)
Sorry, I've been away for a bit due to personal issues. Back now though and will try to get this done this week!
Have there been any updates on this issue? Since the update of July this feature has been disabled in the practical sense (and the early Beta releases have not addressed it either).
With large collections with multiple prompts (whose values change in a daily basis), the current state of affairs is highly disruptive to a normal test workflow, to the point of almost being unbearable.
Has this been released? I see it was closed, but I'm still not seeing prompts if I have a default selected.
OS: Windows 10
Insomnia:
Version 6.2.0
Shell undefined
Node 10.2.0
V8 6.6.346.32
Architecture x64
libcurl/7.57.0-DEV
OpenSSL/1.0.2o
zlib/1.2.11
libssh/1.7.0_DEV
Most helpful comment
Will be fixing this soon