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

As part of a client project, the need arose for our SitefinityContent model to contain the OriginalContentId and Status fields (present in both Sitefinity's Content and DynamicContent models)

When you have time, please update this repository's settings, readme, etc... to be on par with the other sitefinity repository https://github.com/AndcultureCode/AndcultureCode.CSharp.Sitefinity.Testing

• README (overall markdown structure, badges)
• Repo description
• Repo tags

Is this repository a candidate for deletion? Doesn't appear to be used.

See this. Thought is to build something that supports ordering operation on a SitefinityContent object via an expression and therefore can pull the property names strings and types using the object's properties rather than harder code them per the knowledge base article. This could be passed into the find operations in the interface as an operational parameter but it could also be used outside the context of the IDynamicContentRepositoryConductor.cs

Need this to support abstraction of the URL to be able to parse it in a standard way across all dynamic content types.

Noticed a bug in one of our client projects where enumerations would all be set to 0 after MapTo is run to map DynamicContent to a model object.

For one of our client projects, we developed a way to generically create dynamic content items via reflection. Though this was at first just for testing purposes, we now have a need to have functionality available outside of tests. Implement a way to do this so it can be accessible via tests as well as in application code.

in DynamicContentExtensions.cs, the MapTo<T> function has an optional includes parameter. This is a string with multiple include paths, separated by commas, e.g. Product.Orders,Category.ParentCategory.

In order to simplify building these include paths, we should add our helper classes to this repository -- namely IncludeBase.cs, Include.cs, and IncludeExtensions.cs to more easily generate the include paths to be passed into the MapTo<T> function.

These classes are currently contained only in proprietary repos, so an andculture engineer should be contacted to get directed to the existing code.

We created a SitefinityMetadataAttribute attribute as part of a client project to allow for content to be more generically created via reflection. We should port that over to this project for reuse.

For writing testing suite code to support parent relationships, we need a separate ChildSitefinityContent object.

Only Dynamic Sitefinity Content has SystemUrl. All content (dynamic as well) as UrlName but must be a Lstring.

In one of our client repositories, we recently added a ProviderConstants file to keep track of the different data layer providers used for accessing the database. We should port this over so it can be reused in other projects

In a client project, we will soon need the ability to create Dynamic Content via the DynamicContentRepositoryConductor. We should add a Create method definition to this interface to accommodate that.

When Sitefinity maps values represented by enums into the database, they are stored as strings and pulled back out and mapped to Sitefinity's DynamicContent object as a string. This leads to data not being properly mapped from their DynamicContent model to our internal models when using the MapTo method.