heyjaywilson/peakfit

Implement a logger instead of print statements

Open

#19 opened on Sep 24, 2024

View on GitHubContributor guide
 (6 comments) (0 reactions) (1 assignee)Swift (10 forks)auto 404
dev exhacktoberfest

Repository metrics

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

Description

Change all print statements to use Logger from OSLog.

  • Each package should have it's own log category
  • The logger's subsystem should be the product bundle identifier. If you need a default value use dev.cctplus.peakfit
  • The logger should live in the utilities package
  • The logger should be callable using PFLogger()
  • This PR should be labeled as a chore

Resources:

Contributor guide

Research direction
Study the OSLog framework and implement a custom logger in the utilities package with per package categories and a default subsystem identifier. Ensure the logger is callable via PFLogger().
Tech stack
swift
Domain
mobile
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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
SwiftOSLog
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75