acmpesuecc/ShatterLock

Implement appropriate error messages

Open

#5 opened on Oct 17, 2025

View on GitHubContributor guide
 (14 comments) (0 reactions) (0 assignees)C (10 forks)auto 404
Bounty: 50good first issue

Repository metrics

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

Description

Overview

Implement proper error messages, like for a wrong password/username, file does not exist, subdirectory does not exist, etc.

Contributor guide

Research direction
Identify where error messages are missing and add descriptive messages for invalid inputs.
Tech stack
c
Domain
cli
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
CGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75