mirror of
https://github.com/Biarity/Sieve.git
synced 2024-11-22 13:32:33 +01:00
Merge branch 'master' of https://github.com/Biarity/Sieve
This commit is contained in:
commit
ce5da2a573
11
README.md
11
README.md
@ -100,7 +100,16 @@ public class SieveCustomFilterMethods : ISieveCustomFilterMethods
|
|||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
### Configure Sieve
|
## Handle Sieve's exceptions
|
||||||
|
|
||||||
|
Sieve can throw 2 kinds of custom exceptions:
|
||||||
|
|
||||||
|
* `SieveMethodNotFoundException` with a `MethodName`
|
||||||
|
* `SieveIncompatibleMethodException` with a `MethodName`, an `ExpectedType` and an `ActualType`
|
||||||
|
|
||||||
|
It is recommended that you write exception-handling middleware to globally handle Sieve's exceptions when using it with ASP.NET Core.
|
||||||
|
|
||||||
|
## Configure Sieve
|
||||||
Use the [ASP.NET Core options pattern](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options) with `SieveOptions` to tell Sieve where to look for configuration. For example:
|
Use the [ASP.NET Core options pattern](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options) with `SieveOptions` to tell Sieve where to look for configuration. For example:
|
||||||
```
|
```
|
||||||
services.Configure<SieveOptions>(Configuration.GetSection("Sieve"));
|
services.Configure<SieveOptions>(Configuration.GetSection("Sieve"));
|
||||||
|
Loading…
Reference in New Issue
Block a user