Closed tharropoulos closed 3 weeks ago
Just saw that pylint
now fails the check because of duplicate code on the test files. It has to do with not syncing the lock file with the Pipfile
and having an older version of pylint
as a result. Should we break this out on fixtures to avoid rewrites, or add a rule to ignore the duplicate code message in the pylint config file?
This is now available in v0.10.0
Change Summary
Updates the scraper workflow to ensure that user-defined synonyms and curation rules are preserved across runs. Specifically, it adds functionality to copy these rules from the old collection to the new collection before the old collection is deleted. This change helps maintain user configurations without disruption during the scraping process.
Changes include:
PR Checklist