Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Currently, StringSubstitutor is not replacing a variable that is unknown. It would be nice to define the behavior in this case and to allow raising an exception.
A workaround is to define a custom StringLookup that raises an exception when the variable is unknown but this prevent from using the default value feature from StringSubstitutor
Attachments
Issue Links
- links to