Closed benjaminDNUM closed 1 month ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
🎉 Deployment for commit ac8238b18465bac7a33d31fe9efdf35cd9ba07c9 :
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.
:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
close jira 379 (https://jira-mcas.atlassian.net/browse/VAO-379?atlOrigin=eyJpIjoiZjRmMzdkZGE0YzUwNDA5MDhjZTRjMTI1M2I5YmQxYzAiLCJwIjoiaiJ9).
La logique de regénération du token existait deja, mais ne fonctionnait pas : Le watch du composant
validate-token
n'était pas trigger avec les erreurs pour un raison inconnue. Surement un probleme avec nuxt au mount du composant. j'ai changé et utilisé les callbacks de usefetch pour arriver au meme principe.https://www.loom.com/share/09db286d1d284046978aba0059c3aae3?sid=4eb1c989-d834-457d-a206-dadda53cd2b4