Allow for an optional "Order" parameter to be set on implementations of pre, post, and exception handlers. about mediatr HOT 5 CLOSED

Ok, I got outsmarted by multi-targeting support, so this implementation is going to have conditional compilation flags.

from mediatr.

The way I want to support this is directly in the list of pre/post request handlers. There's already an order in the Index property on the list. I don't want to add yet another way of specifying an order when the order is already intrinsically present in the list.

This is a bit different than filters in ASP.NET Core where you have attributes sprinkled all over your codebase with no central registration. I have central registration so that's where you should specify the order.

from mediatr.

@jbogard Apologies for missing the bus with this then. Do you have a link / search term for MediatR's preferred method of registration? This issue came about because of typescanning and auto-registration, but based on whatever your answer is maybe I have a workaround for my issue.

from mediatr.

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

from mediatr.

This issue was closed because it has been stalled for 14 days with no activity.

from mediatr.