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.
Currently if you have a lot of opener_files, 2 issues arise.
It's increasingly difficult for people to know which opener_file does what
If the opener has an author or a repository there is no good way to annotate credit for the contribution in the UI
Describe the solution you'd like
when opener_file is set and the file list of available .json and .txt files is shown, add banner-text or similar to the right of the file name with a users defined annotation (Purpose, Author, Source)
Describe alternatives you've considered
When selecting an opener_file present a pop-up modal which contains the above solution as a "Yes/No" pop up to ensure the user is selecting the opener they wish to.
Additional context
Given that many people are naming their prompts things like "dave" and "dan" and "aim" and on and on and on, while the simple naming convention currently being used for attribution works reasonable well if only running by default, this gets frustrating quickly when more and more prompts are added, and if they have more ambiguous names.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently if you have a lot of opener_files, 2 issues arise.
Describe the solution you'd like
when opener_file is set and the file list of available .json and .txt files is shown, add banner-text or similar to the right of the file name with a users defined annotation (Purpose, Author, Source)
Describe alternatives you've considered
When selecting an opener_file present a pop-up modal which contains the above solution as a "Yes/No" pop up to ensure the user is selecting the opener they wish to.
Additional context
Given that many people are naming their prompts things like "dave" and "dan" and "aim" and on and on and on, while the simple naming convention currently being used for attribution works reasonable well if only running by default, this gets frustrating quickly when more and more prompts are added, and if they have more ambiguous names.
The text was updated successfully, but these errors were encountered: