Closed slushpupie closed 1 year ago
So in this case you expected full to be "This contains part1 (some subtext)" ?
Yes, that is what I expected.
We can make nested subscriptions work but adding it under the current syntax could break existing users code.
I'll add it under new syntax.
Should the LookupPreprocessor handle nested substitutions? The following example does not work, but its not clear from the documentation if it even should work:
It produces an error of
Unresolved substitution This contains part1 (${subtext1}) at (default.conf:1)
If nested substitutions should not work, can at least the documentation be updated to clearly reflect that? I would like them to work, if that can be a feature request.