Improve error handling

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

The issue names no files, tests, or entry points. Start by locating where ValueError, geodiff errors, file and directory errors, and configuration validation errors are currently handled. Done means defining project-specific exceptions and consistently translating these error categories into them.

Written by the indexing model from the issue text.

Description

enhancement

Right now we do not catch errors and emit just some generic errors (e.g. ValueError). It would be good to have a custom error class for our exceptions + handle exceptions from other places and turn them into "our" errors.

Some common errors to handle properly:

  • errors from geodiff
  • file/directory errors (e.g. missing files)
  • something is wrong with configuration (wrong table structure / bad content of tables / ...)
Dominant language
Python
Stars
11
Forks
6
No merged PRs in 30d

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.

More from MerginMaps/work-packages

All issues in MerginMaps/work-packages

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.