You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of the way that properties files work, configuration values may contain trailing whitespaces when read from this type of configuration source. The rationale was to not mess with the value because we don't know if the whitespace is intended or not.
Unfortunately, this seems to cause more harm than good:
The fix usually requires us to go to the problematic property and apply the TrimmingConverter.
Implementation ideas
We could trim automatically every property in the quarkus namespace. This will probably fix all related issues (and future issues) and still keep the original behavior for user configuration.
Potentially, this can be a breaking / inconvenient change even for quarkus configuration. Thinking about properties that set names to be passed to other services that may contain trailing whitespaces, so we need to discuss this carefully.
The text was updated successfully, but these errors were encountered:
Description
Because of the way that
properties
files work, configuration values may contain trailing whitespaces when read from this type of configuration source. The rationale was to not mess with the value because we don't know if the whitespace is intended or not.Unfortunately, this seems to cause more harm than good:
quarkus.jaeger.sampler-param=1
fails to build #5116The fix usually requires us to go to the problematic property and apply the
TrimmingConverter
.Implementation ideas
We could trim automatically every property in the
quarkus
namespace. This will probably fix all related issues (and future issues) and still keep the original behavior for user configuration.Potentially, this can be a breaking / inconvenient change even for
quarkus
configuration. Thinking about properties that set names to be passed to other services that may contain trailing whitespaces, so we need to discuss this carefully.The text was updated successfully, but these errors were encountered: