fix: permitir valores vacíos en librería en enable_auto_register_message_id#13
Merged
Conversation
…guration values. - Upgrade dependency versions, addressing multiple CVEs. - Refactor validator and test cases for improved clarity and expanded blank value handling.
|
AndreyRivera13
changed the title
AndreyRivera13
requested review from
RicharLeon,
avendanodanny and
juannicolas759
and removed request for
RicharLeon
juannicolas759
approved these changes
Jul 7, 2026
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
2 participants
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.
1.Permitir valores vacíos en librería en enable_auto_register_message_id tratarlos como inactivos
Problema
Si el microservicio consumidor declaraba la clave sin valor:
message-id:
enable_auto_register_message_id:
Spring Boot la enlazaba como "" (no null). El validador solo eximía null, así que "" lanzaba BeanInitializationException y tumbaba el arranque.
Solución
Un valor en blanco se trata igual que la propiedad no declarada: no falla al arrancar y el feature queda inactivo por defecto.
MessageIdMngValidator.validate(...): ignora valores en blanco además de null.
MessageIdRequestProperties.afterPropertiesSet(): normaliza blanco a null antes de resolver enabled.
Tests
MessageIdMngValidatorTest: valores en blanco no lanzan excepción.
MessageIdMngUseCaseTest: flag en blanco sin header → null; con header → se propaga.
Compatibilidad
No rompe comportamiento existente; solo tolera un caso que antes crasheaba el arranque.
2.Update dependencies: Jackson core version to 2.21.4, bump logback to 1.5.33, tomcat-embed-core to 10.1.56