codeforpdx / codeforpdx/recordexpungPDX
Update error methods in the crawler
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 93
- Avg merge
- 8m
- Merged PRs (30d)
- 9
Description
The parsers have methods that will run when an error is encountered. These methods need to be implemented so that when an error does occur the user and the dev team can be notified appropriately.
Files to be updated:
- Node Parser https://github.com/codeforpdx/recordexpungPDX/blob/master/src/backend/expungeservice/crawler/parsers/node_parser.py#L16
- Param Parser https://github.com/codeforpdx/recordexpungPDX/blob/master/src/backend/expungeservice/crawler/parsers/param_parser.py#L34
- Record Parser https://github.com/codeforpdx/recordexpungPDX/blob/master/src/backend/expungeservice/crawler/parsers/record_parser.py#L53
This is done when...
- The methods are updated so that it logs the error
- And the methods raise the error so that the user can be notified of the issue
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
Start with the error-handling methods at the listed locations in src/backend/expungeservice/crawler/parsers/node_parser.py, param_parser.py, and record_parser.py. Trace how crawler errors reach these methods and inspect the project's existing logging and error propagation conventions. Done means each method logs the error and raises it so the user can be notified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100