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
The current handling will replace $$ in a value with a single $ - this is due to the internal escaping behavior, which escapes escapes $ as $$. However this behavior isn't documented and can be surprising to users. Should
The $$ is indeed used as an escape sequence to not expand on expressions.
That particular piece is yet another rule added by MP Config, in which \$ should act as an escape sequence for expressions. Please check #746 for more context.
I believe the expression code blindly escapes expressions with the double $, because there is a flag that can be used to omit the brackets and treat the value as an expression. At this stage, we are never going to turn that flag on, so maybe we can make the escape smarter and only work if square brackets are found after?
shawkins
added a commit
to shawkins/smallrye-config
that referenced
this issue
Dec 4, 2023
The current handling will replace $$ in a value with a single $ - this is due to the internal escaping behavior, which escapes escapes $ as $$. However this behavior isn't documented and can be surprising to users. Should
smallrye-config/implementation/src/main/java/io/smallrye/config/ExpressionConfigSourceInterceptor.java
Line 101 in 5a96de2
I don't mind submitting a patch if it's the former.
The text was updated successfully, but these errors were encountered: