search

Azure-Samples / azure-search-openai-demo

A sample app for the Retrieval-Augmented Generation pattern running in Azure, using Azure AI Search for retrieval and Azure OpenAI large language models to power ChatGPT-style and Q&A experiences.
https://azure.microsoft.com/products/search
MIT License
5.6k stars 3.75k forks source link

Customizing? Am I Doing this Wrong? #1630

Open evogelpohl opened 1 month ago

evogelpohl commented 1 month ago

Love the project. However, diving through frontend code to remove/change all the mentions of the default prompts for Northwind HR/healthcare for my use case is taxing. I keep making syntax errors. DOH!

Is there, or should there be a YAML or config file for all the default stuff? E.g. Default Prompts, Notes on the 3 initial cards, Docs to Return, Temp, Search Type, etc...?

I'm not a developer, enthusiast/hack at best, but I thought one principle of dev was to separate all the squishy/config stuff from procedural logic. No? Or, does it work that way, but I'm not doing this right?

Thanks, and keep up the great work. Great project.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ X] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

N/a, general q.

Any log messages given by the failure

N/a, general q.

Expected/desired behavior

N/a

OS and Version?

MacOS.current. Py 3.9. AZD

azd version?

azd version 1.9.2 (commit c58b02f71710960aba28f81f3698e64cfdda9f96)

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

mattgotteiner commented 1 month ago

This is a good idea to create a config file that contains the examples / prompts. This is definitely something we can look at.

pamelafox commented 1 month ago

I have a branch that at least breaks out the prompts. Agreed that its currently not well split up. Thanks for the feedback!

mrmueller commented 1 month ago

We are syncing this repo to Azure DevOps which means we cannot use forking. This makes it harder for us to adopt changes. Splitting up more will make our process easier for sure!