This issue follows a discussion with @grossir, focusing on enhancing the error logging mechanism in Juriscraper, specifically to allow for better logging when a row or document is skipped.
Problem Statement
Currently, Juriscraper may skip certain rows during operations without providing clear and detailed logging. This lack of transparency can be particularly challenging for new users who are trying to understand and debug the process.
Proposed Enhancement
@grossir suggests enhancing the error logging system to include detailed reasons for why a row might be skipped. This enhancement should Log detailed error messages for each skipped row. We already provide custom error logging for Slow, and Insanity exceptions.
Benefits
Ease of Use: Improved error logging will make Juriscraper more user-friendly for newcomers.
Efficient Debugging: Detailed logs will facilitate quicker identification and resolution of issues.
May help use find failures earlier
Example Use Case
In a scenario where Juriscraper skips a row due to a data mismatch, the enhanced logging system would provide a clear message like: "Row skipped due to data format mismatch in column X."
Potential Challenges
Finding the right balance for logging is always a challenge
mlissner
commented
9 months ago
Introduction
This issue follows a discussion with @grossir, focusing on enhancing the error logging mechanism in Juriscraper, specifically to allow for better logging when a row or document is skipped.
Problem Statement
Currently, Juriscraper may skip certain rows during operations without providing clear and detailed logging. This lack of transparency can be particularly challenging for new users who are trying to understand and debug the process.
Proposed Enhancement
@grossir suggests enhancing the error logging system to include detailed reasons for why a row might be skipped. This enhancement should Log detailed error messages for each skipped row. We already provide custom error logging for Slow, and Insanity exceptions.
Benefits
Example Use Case
In a scenario where Juriscraper skips a row due to a data mismatch, the enhanced logging system would provide a clear message like: "Row skipped due to data format mismatch in column X."
Potential Challenges
Call to Action
Any feedback or suggestions are encouraged.