Closed ewan-escience closed 5 months ago
Failed conditions
13.0% Duplication on New Code (required ≤ 3%)
Issues
0 New issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Small question: looking at the code, it seems the frontend needs to know which scrapers there are and what data they produce. It has a has coded list of scrapers and fields like dependents and/or downloads. Wouldn't it be easier in the long run if this solution was more modular and allowed the backend to simply provide a list to the frontend of scraper configs?
We could co that, but it would require us to setup some server with this info. If it becomes a problem later, we can have another look.
More package manager scrapers
Changes proposed in this pull request:
0
is reported whennull
is returned from the database for package managersHow to test:
docker compose down --volumes && docker compose build --parallel && docker compose up --scale data-generation=0
docker compose exec scrapers java -cp /usr/myjava/scrapers.jar nl.esciencecenter.rsd.scraper.package_manager.MainPackageManager
no info
instead of0
Closes #974 Related to #1081
PR Checklist:
docker-compose.yml