using System;
using System.Collections.Generic;
using System.Linq;
using Umbraco.Core.Models;
using Umbraco.Core.Models.PublishedContent;
using Umbraco.Web.Composing;
namespace Umbraco.Web.Models
{
public static class PublishedProperty
{
///
/// Maps a collection of Property to a collection of IPublishedProperty for a specified collection of PublishedPropertyType.
///
/// The published property types.
/// The properties.
/// A mapping function.
/// A collection of IPublishedProperty corresponding to the collection of PublishedPropertyType
/// and taking values from the collection of Property.
/// Ensures that all conversions took place correctly.
internal static IEnumerable MapProperties(
IEnumerable propertyTypes, IEnumerable properties,
Func map)
{
var propertyEditors = Current.PropertyEditors;
var dataTypeService = Current.Services.DataTypeService;
// fixme not dealing with variants
// but the entire thing should die anyways
return propertyTypes.Select(x =>
{
var p = properties.SingleOrDefault(xx => xx.Alias == x.Alias);
var v = p == null || p.GetValue() == null ? null : p.GetValue();
if (v != null)
{
var e = propertyEditors[x.EditorAlias];
// We are converting to string, even for database values which are integer or
// DateTime, which is not optimum. Doing differently would require that we have a way to tell
// whether the conversion to XML string changes something or not... which we don't, and we
// don't want to implement it as PropertyValueEditor.ConvertDbToXml/String should die anyway.
// Don't think about improving the situation here: this is a corner case and the real
// thing to do is to get rig of PropertyValueEditor.ConvertDbToXml/String.
// Use ConvertDbToString to keep it simple, although everywhere we use ConvertDbToXml and
// nothing ensures that the two methods are consistent.
if (e != null)
v = e.GetValueEditor().ConvertDbToString(p.PropertyType, v, dataTypeService);
}
return map(x, v);
});
}
}
}