Skip to content

chore: Remove no longer relevant warning in Designing dependencies documentation page #357

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2025
Merged

chore: Remove no longer relevant warning in Designing dependencies documentation page #357

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 0 additions & 20 deletions Sources/Dependencies/Documentation.docc/Articles/DesigningDependencies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -232,25 +232,5 @@ dependency from the implementation (see
<doc:LivePreviewTest#Separating-interface-and-implementation> 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