ideal-co/ogre

Remove CompletedCheck from BackendMessage

Open

#17 opened on May 21, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (2 forks)auto 404
good first issue

Repository metrics

Stars
 (4 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

We should be in favor of more concrete data when sending the message to a backend, like the ExecResult or we need to better expand the interface for a health.Healthcheck to have more extendable formatting.

Contributor guide

Research direction
Explore how CompletedCheck is currently used in BackendMessage and identify where ExecResult or an expanded Healthcheck interface should replace it. Check existing tests and formatting logic.
Tech stack
go
Domain
backendobservability
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70