Any work on adding Query handler providers/helper classes?
sksallaj82 opened this issue · 5 comments
I've personally adhered to this pattern discussed in this article:
https://cuttingedge.it/blogs/steven/pivot/entry.php?id=92
And I found it to be incredibly simplistic compared to using a repository for my read operations.
Hi.
Are you talking about replacing the repository for the write side, or adding this to the read side? I have not done anything towards this so far. What exactly are you proposing to add? Since all the implementations of IQuery and IQueryHandler are specific to your domain, the only thing that would make sense to add is the QueryProcessor and maybe a few interfaces used by it.
I was thinking of adding support classes to anyone willing to adopt the query handler approach. I happen to like the flexibility that is offered with command handlers, and was thinking the same could be applied for queries as well.
I want to be clear, I didn't mean to mention replacing repository classes in the library. I was initially confused thinking the repository classes were provided as a helper to my own internal repository domain, not as a way to tie into your infrastructure.
Hi. It took a while, but I took a look and decided this was something I could add, and finally had the time to create an API I liked, so I added it to the code. It's now in release 0.26.0