Outdated "RAG Chatbot on your Docs" guide on langbase.com
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 30/100
- Tipo de issue
- Documentación
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Área
- cli, documentation
Línea de trabajo
Locate the source for the Langbase onboarding guides and inspect the BaseAI CLI v0.9.34 flow and generated config. Update the outdated Step 3, document changing the git.include glob patterns, and review the other onboarding guidance and code examples for the stated .env and OpenAI key requirements.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Couldn't find the docs source to make the changes myself, hence opening the issue.
Step 3 in the guide states:
STEP #3 Specify File Extensions
Next, it will ask you which files extensions you want to track. Since we are creating a memory for docs, you can provide a comma-separated list of file extensions like
.mdx,.mdto track markdown files.
However, the current BaseAI CLI (v0.9.34+) does NOT prompt for:
- Directory path to track
- File extensions to track
In version 0.9.34 (November 26, 2024), the memory configuration was simplified. This simplification was updated in the baseAI docs atleast but not in the Langbase onboarding guides leading to uncertainty and friction in the onboarding steps about whether we are using the correct version or if the setup is working properly.
Expected Fix
This among several other details like needing to create .env file for API keys, needing OpenAI keys to start deployment are few more issues which makes me think the onboarding guide is infact outdated and needs some love. Ideally, I would
- Remove Step 3 about file extensions prompt
- Add a step explaining how to modify the
git.includeglob patterns in the generated config file - Review all other onboarding guides and any code examples
- Lenguaje dominante
- TypeScript
- Estrellas
- 92
- Forks
- 24
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de CommandCodeAI/langbase-examples
-
http 500 response Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
CommandCodeAI/langbase-examples#47 · 1 comentario ·
Todos los issues de CommandCodeAI/langbase-examples
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
fil-donadoni/tolaria#4409 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
corsairdev/corsair#1764 ·