From 42fc3745623f599c646b6251576df3d49789b583 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Se=CC=81bastien=20pe=CC=81coul?= Date: Wed, 9 Apr 2025 16:05:34 +0200 Subject: [PATCH] chore: Remove no longer relevant warning in Designing dependencies documentation page --- .../Articles/DesigningDependencies.md | 20 ------------------- 1 file changed, 20 deletions(-) diff --git a/Sources/Dependencies/Documentation.docc/Articles/DesigningDependencies.md b/Sources/Dependencies/Documentation.docc/Articles/DesigningDependencies.md index dca1fa16..56e09ea4 100644 --- a/Sources/Dependencies/Documentation.docc/Articles/DesigningDependencies.md +++ b/Sources/Dependencies/Documentation.docc/Articles/DesigningDependencies.md @@ -232,25 +232,5 @@ dependency from the implementation (see for more information). But now there is no need to maintain that code as it is automatically provided for you by the macro. -> Warning: Due to a [bug in the Swift compiler](https://github.com/apple/swift/issues/71070), -> endpoints that are not throwing will not emit a test failure when invoked. This applies to -> dependencies with endpoints like this: -> -> ```swift -> @DependencyClient -> struct NumberFetcher { -> var get: () async -> Int = { 42 } -> } -> ``` -> -> The workaround is to invoke `reportIssue` directly in the closure: -> -> ```swift -> @DependencyClient -> struct NumberFetcher { -> var get: () async -> Int = { reportIssue("\(Self.self).get"); return 42 } -> } -> ``` - [designing-deps]: https://www.pointfree.co/collections/dependencies [issue-reporting-gh]: http://github.com/pointfreeco/swift-issue-reporting