Multiple issues when upgrading exception handling code to v2

[ThomasArdal]

I'm trying to upgrade Elmah.Io.Functions to support Azure Functions v2. In that context, I have a couple of questions for the new way of developing filters and logging, that I feel are lacking good answers on the official documentation.

1. FunctionExceptionFilterAttribute and FunctionExceptionContext are marked as Obsolete. What is the alternative to exception filters?
2. Previously, I could resolve setting names by doing something like this:

var resolver = new DefaultNameResolver();
var connection = resolver.ResolveWholeString("%connection%");

This is no longer possible, since DefaultNameResolver requires an IConfiguration. I can see why it require that, but I don't have a reference to IConfiguration inside a FunctionExceptionFilterAttribute subclass.

I could start doing something like this:

var configurationBuilder = new ConfigurationBuilder();
...
var config = configurationBuilder.Build();

But I don't know how users are structuring and naming their config files inside the filter.

[fabiocav]

Unfortunately, this feature didn't quite get as polished up as we had hoped for the 3.x release.

Adding @mathewc as he can provide more details.

[ThomasArdal]

Any news on this one?

[ThomasArdal]

@mathewc Would really love some input on this one.

[ThomasArdal]

@fabiocav Do you know anyone else who could input on this?

[sierrapeaks]

@mathewc @fabiocav any status update on this one? thank you

[rasmuschristensen]

Will it get into the new Extensions where we also have DI? Any new status @fabiocav ?

[fabiocav]

Apologies about the lack of response here.

Unfortunately, there hasn't been any work done on filters since our last update. There are a couple of approaches that could potentially work, but that set of APIs is not currently stable, and adopting them would be problematic as it could en up leading to customers impacted by a service upgrade.

Adding @mathewc here in case he has anything else to share.