Repository navigation
Solicitudes: reconocer los ids UUID en avisos y actualización automática - #88
Merged
Merged
Conversation
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
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.
parseRequestIdFromHistoryIdusabaNumber.parseInt, pero los ids de solicitud en Rails son UUID. Con los que empiezan con letra (cerca de 4 de cada 10) devolvíanull, y la solicitud no se reconocía como tal.Efecto: esas solicitudes no activaban la actualización automática ni el aviso al aprobarse o rechazarse. La lista de Movimientos y la campanita no dependen de esta función.
docs/REQUESTS_CONTRACT.md.Pruebas: casos nuevos con UUID en
requestHistory.test.js; eslint yvitest run(493 tests) en verde. No se probó con una solicitud real.