Fixes Issue #38 Returns null if there are no objects in the collection

[ProNotion]

This fixes Issue #38 whereby recursive property lookups were not working as expected when a property with a previous nested content property editor previously had a value which was later removed. See the forum post.

[leekelleher]

Cool, thanks @ProNotion!

Before I merge it in, just want to ping @mattbrailsford for a sanity check ... Matt, do you see any issue with this?

[mattbrailsford]

My only concern is with it now returning null rather string.empty, and did we use string.empty for a reason?

[leekelleher]

I had the same thought, but then noticed that an earlier line returned null.

[ProNotion]

I noticed the same as Lee and changed it for consistency. Returning string.Empty I think did appear to have the same end result.

[mattbrailsford]

all good then

[leekelleher]

Merged, thanks @ProNotion!

[jessetinell]

I just stumbled upon this issue aswell (#38).
Is 0.3.0 planned to be released or is this project on hold? Almost a year since previous release.

[leekelleher]

@jessetinell There are various excuses and delays with us releasing v0.3.0 - mainly that we've been focusing on getting it into the Umbraco core product. (Due in v7.6)

In the meantime, the latest development build of NC can be downloaded from here:
https://ci.appveyor.com/project/leekelleher/umbraco-nested-content/build/artifacts

We also have a MyGet feed if you wanted to use the NuGet package:
https://www.myget.org/feed/umbraco-packages/package/nuget/Our.Umbraco.NestedContent

We're still planning on releasing NC v0.3.0, it's just a matter of us finding the free time to prepare and test it.

[jessetinell]

@leekelleher Ok great, thanks! :)