json-schema-org / json-schema-org/ecosystem
Add Comprehensive Error Handling to Data Collection Scripts
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Problem
The initial-data collection scripts currently lack proper error handling making them vulnerable to:
- Silent failures during API calls
- File system errors during CSV operations
- Unclear error messages when processes fail
Proposed Solution
Add comprehensive error handling to:
GitHub API calls (fetchRepoCreationDate, fetchRepoTopics, etc.)
File operations (DataRecorder class methods)
Main execution flow (runMain function)
Contributor guide
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
Locate the data collection scripts and read the implementations of fetchRepoCreationDate, fetchRepoTopics, the DataRecorder methods, and runMain. Trace how API calls, CSV operations, and the main flow currently report failures. Done means these paths handle errors with clear messages and no longer fail silently; verify the collection scripts still complete successfully for normal inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100