Steve Smith

Logging in the Package

4

Based on these docs: https://learn.microsoft.com/en-us/dotnet/core/extensions/logging-library-authors Is there any logging that would be worthwhile for users of the Specification package (or its Repository base types)?

Docs: Update docs with new FirstOrDefault / SingleOrDefault Repo methods

2

Update docs and README with latest changes in repo methods and ISingleResultSpec changes.

Add FAQ to specification.ardalis.com (docs)

1

Add a FAQ section. Include information about which versions of apps/EF can consume which version of Ardalis.Specification. See #312 for example.

See #53 extension method and #154.

Pull example code/usage from https://github.com/ardalis/Specification/issues/178 https://ardalis.github.io/Specification/features/postprocessingaction.html

See example usage here: https://github.com/ardalis/Specification/pull/192 Boolean can be passed to `.Where`, `.Search` etc. If false, the expression will not be added. Note that `.Select` is not optional - if you...

See: https://github.com/ardalis/Specification/pull/193 Client usage is through `var result = spec.IsSatisfiedBy(customer);`

Add Counting Functionality to Docs

2

See: https://github.com/ardalis/Specification/issues/134#issuecomment-872528093 @fiseni do you think this would be considered a 'base feature'? https://ardalis.github.io/Specification/features/base-features.html If not where should we describe it? Usage?

Consider New Ardalis.Result.FastEndpoints package with base classes, extension methods

2

For example this code from a devBetter.com member: ```csharp public abstract class EndpointBase : Endpoint where TRequest : notnull where TResponse : notnull where TMapper : class, IResponseMapper { public...