MapColonies / MapColonies/schemas
default config name is not validated
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 28m
- Merged PRs (30d)
- 1
Description
I've created a new default config file with a name containing upper-case letters.
The validation passed and config-server ingested.
The request to fetch it is failing with `400` http code.
Also, would like the name to accept upper-case letters because, why not?
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 locating the schema and validation used for default config names, then reproduce the uppercase-name case described in the issue. Check whether validation should reject uppercase names or whether config-server should accept them, and add coverage for the chosen behavior before confirming that fetching the config no longer returns HTTP 400.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100