Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Derived exception classes to identify sources of exceptions

Open
#70 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

Locate the existing dripline_error definition and its derived exception classes, then inspect how service and endpoint errors are constructed and formatted. Define the intended service and endpoint context in the exception messages, with completion requiring a decided design and corresponding behavior for both sources.

Written by the indexing model from the issue text.

Description

A class service_error that derives from dripline_error could take the service name as an argument to the constructor, and it could be automatically placed in the what() text.

Something similar could be done for endpoints, perhaps taking both the parent service name and the endpoint name.

Dominant language
C++
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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 driplineorg/dripline-cpp

All issues in driplineorg/dripline-cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.