eclipse-score / eclipse-score/lifecycle

Make use of static create methods

Open
#488 0 comments 0 reactions 0 assignees View on GitHub
cleanup
Dominant language
C++
Stars
6
Forks
34
Avg merge
2d 3h
Merged PRs (30d)
80

Description

### What

In alive monitor, but also elsewhere, there are `init()`, `construct()`, and other similar method names to handle situations where construction can fail, but we want to handle the error. A cleaner pattern could be to use a static `Create()` method that returns a newly created object or error on failure

### Acceptance Criteria (DoD)

- `construct()` and `init()` methods are removed or made private

### How

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Search the repository for init() and construct(), starting with the alive monitor and other construction paths mentioned in the issue. Identify each affected class and its existing error-handling tests; the work is done when those methods are removed or private and the agreed static Create() pattern covers construction failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.