Jonas Bergqvist
Feb 25, 2011
  5383
(1 votes)

Typed “Find” method in Dynamic data store

On the morning train to work, I played around with the DDS, and made a couple of extension methods to fix something I’ve been irritated about for a while.

The “typed” find method in the DDS takes the name of a property, and the value the property must have to receive the object from the store. This isn’t that nice, and I’m the one to blame. Therefore, I’ve created the following two extensions:

public static IEnumerable<TStore> Find<TStore, TFind>(this DynamicDataStore store, Expression<Func<TStore, TFind>> property, TFind value)
   {
        string propertyName = MultipleFind<TStore>.GetPropertyName<TFind>(property);
        return store.Find<TStore>(propertyName, value);
   }
public static IEnumerable<TStore> Find<TStore>(this DynamicDataStore store, MultipleFind<TStore> find)
{
    return store.Find<TStore>(find.Dictionary);
}

Those extension methods uses the following class that I needed to create:

    public class MultipleFind<TStore>
    {
        private Dictionary<string, object> _find;
        public MultipleFind()
        {
            _find = new Dictionary<string, object>();
        }
        public void Add<TFind>(Expression<Func<TStore, TFind>> property, TFind value)
        {
            _find.Add(GetPropertyName<TFind>(property), value);
        }
        public static string GetPropertyName<TFind>(Expression<Func<TStore, TFind>> property)
        {
            MemberExpression member = property.Body as MemberExpression;
            if (member == null)
            {
                throw new NotSupportedException("Find method only works directly against properties at the moment");
            }
            return member.Member.Name;
        }
        public Dictionary<string, object> Dictionary
        {
            get
            {
                return new Dictionary<string, object>(_find);
            }
        }
    }

Those can be used like this:

var result = _personStore.Find<Person, int>(p => p.ShoeSize, 40);
MultipleFind<Person> findings = new MultipleFind<Person>();
findings.Add(p => p.ShoeSize, 40);
findings.Add(p => p.FirstName, "Jonas");
var result2 = _personStore.Find<Person>(findings);

Compared with:

var result = personStore.Find<Person>("ShoeSize", 40);
Dictionary<string, object> search = new Dictionary<string, object>();
search.Add("ShoeSize", 40);
search.Add("FirstName", "Jonas");
var result2 = personStore.Find<Person>(search);
Feb 25, 2011

Comments

Please login to comment.
Latest blogs
Optimizely’s Sustainability Journey: Creating a Future That’s Built to Last

  For me, sustainability isn’t just a company priority; it’s a personal one. I’m especially mindful of the role that content management plays at th...

Joey Moore | Dec 13, 2024

How I Fixed DLL Conflicts During EPiServer CMS Upgrade to .NET Framework 4.8.1

We had a CMS solution of EPiServer 11.26.0, which was built on .NET Framework 4.7.1. We needed to update the target framework from .NET Framework...

calimat | Dec 12, 2024

Custom form element view in Optimizely CMS 12

Do you want full control over the form element markup? Create your own views!

Tomas Hensrud Gulla | Dec 11, 2024 | Syndicated blog

How to Elevate Your Experimentation - Opticon workshop experience

As a non-expert in the field of experimentation, I’d like to share my feedback on the recent Opticon San Antonio workshop session titled "How to...

David Ortiz | Dec 11, 2024

Persisting a Strawberry Shake GraphQL Client for Optimizely's Content Graph

A recent CMS project used Strawberry Shake to generate an up-to-date C# GraphQL client at each build. But what happens to the build if the GraphQL...

Nicholas Sideras | Dec 11, 2024 | Syndicated blog

Opti ID with Secure Cookies And Third Party AddOns

Opti ID has revolutionised access to the Optimizely One suite and is now the preferred authentication method on all PAAS CMS websites that I build....

Mark Stott | Dec 9, 2024