[
https://issues.apache.org/jira/browse/TEXT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667556#comment-16667556
]
ASF GitHub Bot commented on TEXT-127:
-------------------------------------
GitHub user drajakumar opened a pull request:
https://github.com/apache/commons-text/pull/91
TEXT-127 Detect when a variable is unknown in StringSubstitutor
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/drajakumar/commons-text master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/commons-text/pull/91.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #91
----
commit d3bfb518ccde125b45b9d7a874cf717321578e7f
Author: Don Jeba <donjeba@...>
Date: 2018-10-29T18:05:19Z
TEXT-127 Detect when a variable is unknown in StringSubstitutor
----
> 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)
