Do not treat .prompty files as scripts by default

[waldekmastykarz]

Feature Proposal

Request:
Do not treat .prompty files as scripts by default in genaiscript.

Rationale:

• Many developers choose to store prompts separately from scripts for easier debugging and maintainability.
• In VSCode, having .prompty files appear in the list of scripts can create confusion and clutter.
• If users prefer not to use .prompty files as scripts, they should be able to name them the same as their scripts without genaiscript complaining about duplicate scripts.
• This would allow for more flexible project structures and improve the developer experience when managing scripts and prompts.

Expected Behavior:

• .prompty files should not be treated as scripts by default.
• There should be a way to hide .prompty files from the script list in VSCode.
• Naming a .prompty file the same as a script file should not result in a duplicate script error if the user is not using .prompty files as scripts.

Additional Context:

• This feature would support workflows where prompts are managed independently of scripts, improving maintainability and clarity.

[github-actions]

Thank you for the detailed proposal. Your rationale is clear, and the expected behavior is well outlined. To help further, could you clarify:

• In your workflow, are there ever cases where a .prompty file should be runnable as a script, or should they always be excluded by default?
• Would you want a configuration option to treat .prompty files as scripts in rare cases, or is the current default behavior fine as long as .prompty files can be excluded from the script list and duplicate detection?
• Are there other file extensions you use for prompts (besides .prompty) that should be handled similarly, or is this request specific to .prompty?

Your feedback will help ensure the implementation supports flexible project structures without introducing unintended side effects.

AI-generated content by issue-reviewer may be incorrect. Use reactions to eval.

[waldekmastykarz]

• In your workflow, are there ever cases where a .prompty file should be runnable as a script, or should they always be excluded by default?

Not at the moment

• Would you want a configuration option to treat .prompty files as scripts in rare cases, or is the current default behavior fine as long as .prompty files can be excluded from the script list and duplicate detection?

Could be convenient to have an option for it, but so far I haven't ran into such a need

• Are there other file extensions you use for prompts (besides .prompty) that should be handled similarly, or is this request specific to .prompty?

This is specific to Prompty.

[pelikhan]

.prompty files will be ignored in 2.0 (you can test this with npm)