Feature#462v2 #597
Feature#462v2 #597
Conversation
…HandlerTest para soportar completamente los patrones reactivos.En total se han ajustado 6 métodos del GlobalExceptionHandler y 8 test asociados en GlobalExceptionHandlerTest.Todos los manejadores de excepciones ahora retornan Mono<ResponseEntity<MessageDto>> para mantener la operación asincrónica y no bloqueante.
# Conflicts: # itachallenge-challenge/src/main/java/com/itachallenge/challenge/controller/ChallengeController.java
…guage/{idLanguage
# Conflicts: # itachallenge-challenge/src/main/java/com/itachallenge/challenge/controller/ChallengeController.java # itachallenge-challenge/src/main/java/com/itachallenge/challenge/exception/GlobalExceptionHandler.java
… refactoring test
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| @@ -301,7 +323,7 @@ | |||
| boolean validUUID = !StringUtils.isEmpty(id) && UUID_FORM.matcher(id).matches(); | |||
|
|
|||
| if (!validUUID) { | |||
| log.warn("Invalid ID format: {}", id); | |||
| log.warn("Invalid ID format."); | |||
Check notice
Code scanning / SonarCloud
Logging should not be vulnerable to injection attacks Low
There was a problem hiding this comment.
Fix Delete and Patch methods:
The behavior of the Patch method was corrected. Previously, it was functioning similarly to Delete.
Now, Patch allows updating all fields or just one field as needed.
Added update method in ChallengeService: A new update method was introduced in ChallengeService to handle both partial and full updates of challenges.
Improved log data handling for security: Adjustments were made to ensure that user-controlled data, such as IDs or parameters, are no longer logged, addressing potential security concerns and preventing exposure of sensitive information.
|
Normalización de excepciones.