[
https://issues.apache.org/jira/browse/TEXT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670031#comment-16670031
]
ASF GitHub Bot commented on TEXT-127:
-------------------------------------
Github user drajakumar commented on the issue:
https://github.com/apache/commons-text/pull/91
closed the pr as @garydgregory made applied a different patch that changes
the instance variable name and method name. He also provided the variable name
that is not found. He added some missing Javadoc throws tags.
https://github.com/apache/commons-text/commit/ed94773e2d2e4da4e993e5a50ee72624587cf76b
> Add a toggle to throw an exception 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
> Fix For: 1.7
>
>
> 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)
