Legacy Project Configs should be upgraded
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.2k
- Forks
- 1.8k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 6
Description
There are legacy config settings used in some examples, such as python/flask/vercel.json, which could be updated to use rewrites and other current project configuration options.
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 with python/flask/vercel.json and compare its legacy settings with the current project configuration options in the linked Vercel documentation. Then inspect the other examples for similar legacy configurations; done means the affected examples use current options such as rewrites instead of legacy settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100