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
Is your feature request related to a problem? Please describe.
It would be interesting if individual prompts tracked their own submission history
Describe the solution you'd like
This could be an option enabled via something like updateSettings({ history: { id: 'my-package' } }), which would then create and store global prompt history for open ended input prompts. Each of those would need a unique ID, and we'd need to key the history against the package version as well.
Describe alternatives you've considered
Is this even a good idea? We could not implement this! Which, tbh, is also perfectly valid.
Additional context
See discussion thar sparked this idea in #186
The text was updated successfully, but these errors were encountered:
As an alternative, text prompt could provide history: string[] option, which would allow users to have greater control over available history (e.g. filtering out some entries).
However, when pressing Enter, TextPrompt would ignore this.value I've set in the cursor event and use this.value = this.rl?.line.replace(/\t/g, ''); from prompt.ts. When I would disable track option I've lost ability to display text. 🤷♂️
Is your feature request related to a problem? Please describe.
It would be interesting if individual prompts tracked their own submission history
Describe the solution you'd like
This could be an option enabled via something like
updateSettings({ history: { id: 'my-package' } })
, which would then create and store global prompt history for open ended input prompts. Each of those would need a unique ID, and we'd need to key the history against the package version as well.Describe alternatives you've considered
Is this even a good idea? We could not implement this! Which, tbh, is also perfectly valid.
Additional context
See discussion thar sparked this idea in #186
The text was updated successfully, but these errors were encountered: