[ https://issues.apache.org/jira/browse/TEXT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662917#comment-16662917 ]
Gary Gregory commented on TEXT-127: ----------------------------------- The best path is to submit a PR on GitHub IMO. I would make sure the current behavior is not broken, IOW, don't throw an exception unless I call an API to enable it. Don't forget unit tests ;-) > Detect when a variable is unknown in StringSubstitutor > ------------------------------------------------------ > > Key: TEXT-127 > URL: https://issues.apache.org/jira/browse/TEXT-127 > Project: Commons Text > Issue Type: Improvement > Reporter: Jean-Baptiste REICH > Priority: Minor > > 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)