Remove support for legacy configuration files
Open
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 121
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 29
Description
## Short description
In #3011 we replaced Java properties files with HOCON conf files instead. These are better due to the ability to configure lists and objects as well as simple key-value pairs.
#3043 was created for this but due to ongoing use of properties files by the BBC it has been closed for now.
Contributor guide
Research direction
Read issues #3011 and #3043 first to understand the HOCON migration and why legacy properties files remain in use. Locate the configuration-loading code and its tests, then determine what must be removed so HOCON is the only supported configuration format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100