MapColonies / MapColonies/config-server
having config name as unique vs name and schema
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Today the config name is unique and cannot be duplicated at all.
we might consider changing it so name and schema combination will be unique.
this will make it so we can create multiple versions with the same name and will make schema upgrades easier.
the problem is it will make it harder to make api calls, and to reference configs by name as its combined.
Contributor guide
No contributing guide indexed for this repository
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 how configs are stored and looked up by name in the API. Define how name-and-schema uniqueness, multiple versions, and config references should work, then verify the API behavior and schema-upgrade impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100