PhilflowIO/tsdav

Improve error messages and troubleshooting

Open

#17 opened on Oct 28, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (0 forks)auto 404
documentationenhancementgood first issuephase-2

Repository metrics

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

Description

Make error messages more helpful and actionable.

Requirements:

  • Detailed error codes with links to documentation
  • Suggest fixes for common errors
  • Export detailed error log (JSON format)
  • Integration with --debug flag

Example:

Error: Authentication failed (HTTP 401)
Possible causes:
  1. Invalid credentials
  2. OAuth token expired
  3. Insufficient permissions

Troubleshooting steps:
  - Verify credentials in .env file
  - Regenerate OAuth refresh token
  - Check API permissions in Google Cloud Console

For more help: https://docs.example.com/errors/AUTH_401

Estimated Effort: Small (2 days)

Related to: DAV Migration CLI - Phase 2

Contributor guide

Research direction
Study the existing error handling in the codebase, identify key error points (e.g., authentication, API requests), and implement the pattern suggested in the issue: detailed error codes with docs links, suggested fixes, JSON error log export, and integration with the ` debug` flag.
Tech stack
typescript
Domain
developer experiencecli
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-2 days
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
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75