rsm-hcd / andculturecode.csharp.sitefinity.conductors Goto Github PK

Via using this in a client project, we discovered that Sitefinity is handling enumerations in such a way that they need to be handled differently. Specifically, Sitefinity's ChoiceField (i.e. select dropdowns) store values as strings, meaning corresponding enum values need to be set as a string when adapting one of our models to a DynamicContent object.

See this. Update the interface's implementation to use the ordering capability.

In a client project, we will soon need the ability to create Dynamic Content via the DynamicContentRepositoryConductor. We should add that functionality here to accommodate that.

See also: rsm-hcd/AndcultureCode.CSharp.Sitefinity.Core#7

See DynamicContentExtensions.MapTo<>()

if (dynamicProperty == null || dynamicProperty.PropertyType != property.PropertyType)
{
    continue;
}

Instead of continuing here, this should throw an exception. The thought being that this should only be used for the models we define and should always match the content type of the dynamic model that Sitefinity is using. This is for information purposes so developers know, if it happens, that it is happening. Otherwise, fields can fail to map appropriately and the developer wouldn't be aware of it in all cases.