Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

feat: multi-wire gateway profile and provider-registry conformance tests

Abierto
  • ¿Algo no está bien?
#146 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
api, backend, testing

Línea de trabajo

The issue proposes a new gateway profile and conformance tests. Start by examining the existing provider registry and model routing code in the repository. Look for existing tests related to streaming, tool calls, and error handling (401, 404, 429). Determine how models are currently mapped to wires and what changes are needed to make them explicit. 'Done' would be a working implementation and passing tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
Feature Description

Hi — we represent A2Agent. Kit's provider registry, models.dev routing, custom OpenAI-compatible support and provider overrides appear to offer a clean way to represent an aggregator without adding a parallel registry.

We would like to propose a provider-neutral gateway profile in which each returned or configured model maps to an explicit wire, followed by tests for streaming text, incremental tool calls and 401/404/429 behavior. This avoids assuming that every model behind one base URL is OpenAI-shaped or that model names reliably identify the protocol. An A2Agent example can demonstrate the profile if maintainers want one.

Would you prefer a generic registry fixture, an override example, or both? Is there another mapping mechanism we should follow?

Separately, with permission, we would like A2Agent to be listed factually in the README or GitHub project page under Integrations, Supported Providers, Partners, Sponsors, or another section you select. Please confirm the link request separately and specify location, wording and whether a logo is allowed. We will not submit a link-only PR or imply endorsement.

Motivation / Use Case

A2Agent can provide a private test key, compatibility testing, documentation and long-term maintenance. Eligible open-source compatibility work may receive $20–$100 in non-cash API credits, with possible continuing credits for an active integration. Support is not conditional on a merge, endorsement, referral or link display.

Proposed Implementation
Alternatives Considered
  • I've considered workarounds or alternative approaches
Checklist
  • I've searched existing issues and this hasn't been requested yet
  • This feature aligns with Kit's design philosophy (TUI-first, extension-based)
Lenguaje dominante
Go
Estrellas
139
Forks
24
Merge medio
5 h 29 min
PR fusionados (30 d)
29

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de mark3labs/kit

Todos los issues de mark3labs/kit

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.