GitHub user mortensoby opened a pull request:
https://github.com/apache/groovy/pull/465
null-safe and empty-safe number parsing of xml
The following results in af NumberFormatException:
xml.'**'.find{it.name()` == 'someBigDecimal'}.toBigDecimal()
if the element content is empty which means the following construct is
necessary:
```
xml.'**'.find{it.name() == 'someEmptyBigDecimal' &&
it.text()}?.toBigDecimal()
```
This pull request ensures that null is returned if the element is empty for
the following methods:
```
toBigInteger()
toBigDecimal()
toDouble()
toBigLong()
toBigFloat()
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mortensoby/groovy master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/groovy/pull/465.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 #465
----
commit 9cafd9d44fbcdb71b574664dadf87be1aa4ec06b
Author: Morten Holm Søby <m...@nineconsult.dk>
Date: 2016-11-25T14:39:46Z
null-safe and empty-safe number parsing of xml
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
