chroma-core/chroma

Replace ValueError/TypeError with InvalidArgumentError

Open

#3026 opened on Oct 29, 2024

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Rust (27,958 stars) (2,247 forks)batch import
by-chromaenhancementgood first issue

Description

Describe the problem

All instances where chroma throws ValueError/TypeError should be replaced with InvalidArgumentError

Describe the proposed solution

^

Alternatives considered

No response

Importance

nice to have

Additional Information

No response

Contributor guide

Tech stack
python
Domain
backenddeveloper experience
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
python basicschroma codebase navigation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Search the entire chroma codebase for instances of ValueError and TypeError that are raised directly. Replace each with InvalidArgumentError. Ensure that the custom error class InvalidArgumentError is imported and used consistently. Check for any imports of ValueError or TypeError that may be used in custom exceptions and update those as well.