ballercat / ballercat/jambox

Surface failed requests to the user (other than logs)

Open
#16 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
11
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Sometimes requests could fail due to various reasons. For example, when attempting to integrate with some development/local service a local issuer certificate error might be encountered which can be fixed by adding the dev host to a `trust` hosts array in the config.

The problem is, if something like that is happening it's difficult to catch because it's not surfaced to the user that these requests are failing.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by locating request handling, the existing log path, and the configuration containing the trust hosts array; determine where failed requests can be observed. Done means users can tell when requests fail without consulting logs, including errors such as local issuer certificate failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.