[
https://issues.apache.org/jira/browse/TEXT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669452#comment-16669452
]
Gary Gregory edited comment on TEXT-127 at 10/31/18 12:21 AM:
--------------------------------------------------------------
I applied a different patch that changes the instance variable name and method
name. I also provided the variable name that is not found. I added some missing
Javadoc throws tags.
Please verify and close the PR and this ticket.
was (Author: garydgregory):
I applied a different patch that changes the instance variable name and method
name. I also provided the variable name that is not found. I added some missing
Javadoc throws tags.
Please verify and close the PR and this ticket.
> 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)
