From e244d50d52d5e70788451e69d3c7d996a2832c49 Mon Sep 17 00:00:00 2001 From: Steve Smith Date: Tue, 2 Aug 2022 12:02:52 -0400 Subject: [PATCH] Update README.md --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 72d7f138..37a78f89 100644 --- a/README.md +++ b/README.md @@ -53,6 +53,8 @@ Base class with tests for adding specifications to a DDD model. Also includes a - Implement infrastructure for specification validators. [Issue #111](https://github.com/ardalis/Specification/issues/111) +- `GetBySpecAsync` and similar methods are marked obsolete; prefer `FirstOrDefault` or `SingleOrDefault` instead. + ## Sample Usage The Specification pattern pulls query-specific logic out of other places in the application where it currently exists. For applications with minimal abstraction that use EF Core directly, the specification will eliminate `Where`, `Include`, `Select` and similar expressions from almost all places where they're being used. In applications that abstract database query logic behind a `Repository` abstraction, the specification will typically eliminate the need for many custom `Repository` implementation classes as well as custom query methods on `Repository` implementations. Instead of many different ways to filter and shape data using various methods, the same capability is achieved with few core methods.