0xPlaygrounds / 0xPlaygrounds/rig

refactor: split rig providers into own crate

Offen
#741 1 Kommentar 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen
feat
Vorherrschende Sprache
Rust
Sterne
8.6k
Forks
959
Ø Merge
4 Std. 32 Min.
Gemergte PRs (30 T.)
117

Beschreibung

- [x] I have looked for existing issues (including closed) about this

## Feature Request

The title is self explanatory.

### Motivation

The rationale behind this is that if we split the providers into its own crate, users are then able to essentially use whatever providers they want without anything else.

I think this is important because it does seem that Rust is missing a good crate just for calling LLMs.

### Proposal

Split the `rig::providers` module into its own crate. That's pretty much it.

### Additional
I will be assigning this work to myself as this is a very large change with sweeping implications if this gets accepted.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

The providers module is currently in rig::providers. Examine its structure, dependencies, and how it's used throughout the codebase. The goal is to extract it into a separate crate, which involves updating Cargo.toml, managing public/private APIs, and ensuring downstream usage remains compatible. Start by reviewing the existing module and its integration points.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
rust
Bereich
backend-api-design, tooling
Issue-Typ
Refactoring
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.