fix: correcciones de routing SPA, expiración de token y carga inicial del tablero#14
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.
What
Corrige tres bugs de experiencia de usuario: error 403 al recargar rutas del SPA, falta de redirección al login cuando el token expira, y carga innecesaria de todas las tareas al entrar al tablero.
Why
/projects, Spring Security bloqueaba la petición con 403 porque no reconocía las rutas del frontend.Changes
SecurityConfig.java: reordenar reglas para que/api/**requiera autenticación y todo lo demás sea público (rutas SPA)SpaController.java(nuevo): reenvía rutas sin extensión aindex.htmlpara que React Router las manejeJwtAuthFilter.java: cuando el token está presente pero inválido/expirado, responde con 401 en lugar de dejar pasar la petición sin autenticaciónTasksPage.jsx: inicializarfilters.sprintcomoundefinedpara bloquear la carga inicial hasta determinar el sprint; ampliar el fallback al sprint más reciente por fecha (cualquier estado, no solo PLANNING)