Skip to main content

Generic Comparer

A requirement in most of our applications is a default sorting for our codetable data. For example if you want to populate a combobox with all the countries in the world, it must be sorted by default in alphabetical order.

I heard my colleagues discussing about it during one of our whiteboard design meetings. Possibilities passed by from using a custom attribute to a metadata class. While they were discussing I build the following solution; a generic comparer.

Specify the properties to sort on using expressions and pass it on to the Sort method. No direct coupling between a class and it's sorting, type safety and extensible. What do you need more?

The implementation of the Comparer is very simple, it just iterate over the expressions array and compares each property in both objects: 

   1:  public class GenericComparer<T> : IComparer<T>
   2:  {
   3:          private readonly Func<T, IComparable>[] _expressions;
   4:   
   5:          public GenericComparer(params Func<T, IComparable>[] expressions)
   6:          {
   7:              _expressions = expressions;
   8:          }
   9:   
  10:          public int Compare(T x, T y)
  11:          {
  12:              foreach (var expression in _expressions)
  13:              {
  14:                  int result = Compare(expression.Invoke(x), expression.Invoke(y));
  15:                  if (result != 0)
  16:                      return result;
  17:              }
  18:              return 0;
  19:          }
  20:   
  21:          private int Compare(IComparable x, IComparable y)
  22:          {
  23:              if (x == null && y == null)
  24:                  return 0;
  25:              if (x == null)
  26:                  return -1;
  27:              if (y == null)
  28:                  return 1;
  29:              return x.CompareTo(y);
  30:          }
  31:   }

And an example:

   1:  countries.Sort(new GenericComparer<Country>(c => c.CountryCode, c => p.Name));

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...