C# Generic Messaging Pattern

I'm not sure if I can do this or not, but I am building the service layer of an application which needs to add one type of entity to another. An example might be adding an article to a category. It does this through a service class, for example:
 
 
public class ArticleService { 
     public IResponse AddArticleToCategory(IAddRelatedItemRequest<Category, Article> request) { 
     // do stuff with the request 
     } 
}

Open in new window


I would like the IAddRelatedItemRequest interface to be generic so it can be used for any addition request, similar to:

 
public interface IAddRelatedItemRequest<T, U> 
where T : class 
where U : class { 
    Object Key { get;set; } 
    List<Object> RelatedKey { get;set; } 
}

Open in new window


What is happening is that the request requires the primary key of the item (e.g. the category) and a list of the primary keys of the related items (e.g. the articles). The AddCommentToArticle class in the concrete ArticleService then retrieves the item by its key and then adds the related key items to it.   Note that the primary keys of the entities are not necessarily integers, they could be uniqueidentifiers.

I want to strongly type the request somehow, so instead of an object and a list of objects being supplied, the interface takes the types of the primary keys of the two entities.

The intereface would then look something like

 
public interface IAddRelatedItemRequest<T, U> 
where T : class 
where U : class { 
    TPrimaryKeyType Key { get;set; } 
    List<UPrimaryKeyType> RelatedKey { get;set; } 
}

Open in new window


Obviously this code is not correct but illustrates the end result.

Ideally I would like to somehow extract the type of the entity's Id from the generic type and include that in the interface. Is this possible?

Note:
What I don't want to happen is supply the actual entity and a list of related entities - it needs to be done through primitive primary keys.
I don't particularly want to supply the two types through Generics as it makes for less readable code and the keys of the objects could potentially change type.
pipelineconsultingAsked:
Who is Participating?
 
SriVaddadiConnect With a Mentor Commented:
Define an interface  
like
interface IPrimaryKey
{
    T Key {get;set;}
    List<T> RelatedKey {get;set;}
}

public interface IAddRelatedItemRequest<T, U>
where T : class
where U : IPrimaryKey

Means that your Article class has to implement IPrimaryKey interface and could specify the type

HTH
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.