docs: añadir sección de bugs reales al README - #4
Merged
Conversation
expense-tracker-ui documenta el bug de ExpenseUpdate.date desde su lado, pero expense-api -- donde vive el bug y su fix con test de regresion (c3fb120) -- nunca tuvo una seccion equivalente. Mismo patron que personal-rag-assistant/-ui: cerrar la inconsistencia en el proyecto 1 del portfolio.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #3
Qué cambia
Nueva sección "Bugs reales encontrados construyendo esto", mismo estilo que el resto del portfolio. Documenta el bug de
ExpenseUpdate.date(shadowing de nombres en Python) desde la perspectiva del backend -- donde vive el bug real y su fix con test de regresión (commitc3fb120) -- que hasta ahora solo se contaba desdeexpense-tracker-ui.No se añaden entradas para pines preventivos (p. ej.
bcrypt==4.0.1) que estuvieron en elrequirements.txtdesde el primer commit sin haberse manifestado nunca como un bug real observado en este repo -- eso es conocimiento de ecosistema ya capturado en la Skillscaffold-fastapi-backend, no un bug encontrado aquí.Test plan