Consider config file dependencies
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 621
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
The web app currently has to import the full MultiScanner just to determine the location of the web_config file. For distributed MultiScanner it would be nice if everything the web app needs was contained in /web so it wouldn't need all of MultiScanner's modules and dependencies.
I don't know that the name of the config file needs to be configurable by the user. If it wasn't an option in the main MultiScanner config.ini, web/app.py wouldn't need to load config.ini.
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 web/app.py and trace how it imports MultiScanner and loads config.ini to locate web_config. Review the /web boundary and the main MultiScanner config.ini option described in the issue. Done means the web app can locate web_config without importing unnecessary MultiScanner modules and dependencies, with the configurability decision made explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100