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

Guardrails: Inline validator support

Cerrado
  • ¿Algo no está bien?
#1,247 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@AkhileshNegi ya está trabajando en esto.

Desde el 14/10/2026.

  • #1245 de @AkhileshNegi — fusionado

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement

Is your feature request related to a problem?
Guardrail entries in an LLM config can only reference a saved validator_config_id, preventing direct definition of validators and requiring deletion to disable, which loses setup.

Describe the solution you'd like

  • Allow guardrail entries to be a validator_config_id or an inline validator spec (type, on_fail, per-type params).
  • Restrict inline type to gender_assumption_bias, pii_remover, profanity_free, topic_relevance_llm.
  • Add an is_enabled flag (default true) to both entry types. Disabled entries remain saved but are not fetched or sent.
  • Send validators in config order to the guardrails service. Include stage on inline specs and remove is_enabled to comply with validator schemas.
Original issue

Is your feature request related to a problem?
Guardrail entries in an LLM config blob (input_guardrails / output_guardrails) can only reference a validator_config_id saved in the guardrails service. A validator cannot be defined directly in the config, and the only way to turn one off is to delete it from the config version, which loses its setup.

Describe the solution you'd like

  • Let each guardrail entry be either a validator_config_id reference or an inline validator spec (type, on_fail, per-type params).
  • Restrict inline type to gender_assumption_bias, pii_remover, profanity_free, topic_relevance_llm for now.
  • Add an is_enabled flag (default true) to both entry kinds. Disabled entries stay saved in the config version but are never fetched or sent to the guardrails service.
  • Send validators to the guardrails service in config order. Stamp stage on inline specs and strip is_enabled, since the service's validator schemas forbid extra fields.

Comments: Implemented in #1245.

Lenguaje dominante
Python
Estrellas
18
Forks
11
Merge medio
4 d 3 h
PR fusionados (30 d)
13

Preparar el entorno

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 ProjectTech4DevAI/kaapi-backend

Todos los issues de ProjectTech4DevAI/kaapi-backend

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.