SpaceTeam/STS1_EDU_Scheduler

Properly handle config data

Open

#129 opened on Dec 3, 2023

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Rust (0 forks)auto 404
Featureenhancementgood first issue

Repository metrics

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

Description

Currently, we read configuration data from a config.toml file in the working directory.

This should be improved to

  • load the config file not in main, but in a global (see lazy_static)
  • add more config options like
    • maximum result file size
    • CEP timeouts

Contributor guide

Research direction
Study lazy static usage. Refactor config loading from main to lazy static. Add fields for max result file size and CEP timeouts.
Tech stack
rust
Domain
backend
Issue type
Feature
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75