microsoft / microsoft/azurechat
Extensions and Personas should not be in History container
Open
Nobody has claimed this yet.
bug
enhancement
help wanted
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
I can see we are storing Extensions and Personas configuration in CosmosDB - History container.
Should we store them in Config container where we already store Prompt entity that will make more sense than History container?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where Extensions and Personas are persisted in the CosmosDB History container, then compare that path with the existing Prompt entity in the Config container. Confirm the intended container and the migration or compatibility implications before changing anything; done means the storage design is agreed and the affected persistence behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100