[
https://issues.apache.org/jira/browse/TEXT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667580#comment-16667580
]
ASF GitHub Bot commented on TEXT-127:
-------------------------------------
Github user coveralls commented on the issue:
https://github.com/apache/commons-text/pull/91
[](https://coveralls.io/builds/19787137)
Coverage increased (+0.002%) to 97.876% when pulling
**60bed4374a2db82bc7842d3ccd33e2158d2b80f6 on drajakumar:master** into
**6c3cc5239c2143256976c9e8a05dd76b31c74baf on apache:master**.
> 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)