codeforpdx / codeforpdx/recordexpungPDX

Update error methods in the crawler

Open
#22 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backend enhancement not ready 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:

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.