-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Proposal] Implement Global Configuration and Scripts for genaiscript #834
Comments
Sounds good. What kind of format would you typically want this file to be? |
YAML would be the preferred choice, with JSON as a secondary option. |
Start of global config in #858 |
@borgius in 1.75.0, you can start to specify a global .env with the configuration files at https://microsoft.github.io/genaiscript/reference/configuration-files/ |
(1.75.0 is live). |
@borgius the configuration files now support a |
Proposition: Global Genai Scripts
Core Functionality
~/.genai
file for global configuration:globalScripts
).env
filename in a project (e.g., storing a.env
file with global config in the repo, while using.env.local
in.gitignore
)VSCode Extension
~/.genai
by default)global
folder to list scripts from theglobalScripts
folderRationale
Currently, it's required to save global Genai scripts within the current project's directory. This can be inconvenient, as users may want to maintain a set of global scripts that can be used across multiple projects.
By introducing a global configuration file (
~/.genai
) and allowing users to specify a folder for global scripts, users can more easily manage and reuse their Genai scripts across different projects. This will improve the overall developer experience and make it easier to maintain a consistent set of global Genai scripts.The VSCode extension updates will further enhance the user experience by providing a dedicated interface for accessing and managing the global Genai scripts, making it more discoverable and accessible for developers.
The text was updated successfully, but these errors were encountered: