[ 
https://issues.apache.org/jira/browse/TAMAYA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620802#comment-16620802
 ] 

ASF GitHub Bot commented on TAMAYA-350:
---------------------------------------

GitHub user alexsuter opened a pull request:

    https://github.com/apache/incubator-tamaya-extensions/pull/7

    TAMAYA-350 - Do not provide null as "null" string

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/alexsuter/incubator-tamaya-extensions master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-tamaya-extensions/pull/7.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 #7
    
----
commit 89392d4c4f8c3deb09ee875c8583a9ee20aaca67
Author: Alex <alexander.suter.ch@...>
Date:   2018-09-19T16:16:00Z

    TAMAYA-350 - Do not provide null as "null" string

----


> Empty entry handling YAML Property Source
> -----------------------------------------
>
>                 Key: TAMAYA-350
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-350
>             Project: Tamaya
>          Issue Type: Bug
>    Affects Versions: 0.3-incubating
>            Reporter: Alexander Suter
>            Priority: Major
>
> The YAML Format handles empty entries not nice.
> If I define a yaml like that:
>  
>  
> {code:java}
> myYaml:
>   myProperties:{code}
>  
> And now query my myYaml.myProperties -> I get a String *"null".* Instead of 
> null.
> The problem is here:
> {code:java}
> org.apache.tamaya.yaml.YAMLFormat.mapValueToString(Object){code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to