From c8df1c8824deea91cf992e81370a2279675da9bb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Harrtell?= Date: Thu, 13 Feb 2025 17:07:50 +0100 Subject: [PATCH] Note single project req. in common pitfalls --- docs/usage/common-pitfalls.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/usage/common-pitfalls.md b/docs/usage/common-pitfalls.md index f1f3fed3d6..115f41c55e 100644 --- a/docs/usage/common-pitfalls.md +++ b/docs/usage/common-pitfalls.md @@ -143,3 +143,7 @@ A better way is to inject your `DbContext` in a [Resource Definition](~/usage/ex While we'd love to support such [tokens for optimistic concurrency](https://learn.microsoft.com/en-us/ef/core/saving/concurrency?tabs=data-annotations), it turns out that the implementation is far from trivial. We've come a long way, but aren't sure how it should work when relationship endpoints and atomic operations are involved. If you're interested, we welcome your feedback at https://github.com/json-api-dotnet/JsonApiDotNetCore/pull/1119. + +#### Source generation features doesn't work on code in separated projects + +See https://github.com/json-api-dotnet/JsonApiDotNetCore/issues/1511.