Skip to content

Commit 23af7e5

Browse files
authored
Fix some broken links in Documentation (#1003)
I periodically run a broken link checker over swiftlang repositories. There were a few links pointing to outdated locations in swift-testing.
1 parent ad8a13f commit 23af7e5

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

Documentation/ABI/JSON.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ See https://swift.org/CONTRIBUTORS.txt for Swift project authors
1313
This document outlines the JSON schemas used by the testing library for its ABI
1414
entry point and for the `--event-stream-output-path` command-line argument. For
1515
more information about the ABI entry point, see the documentation for
16-
[ABI.v0.EntryPoint](https://github.com/search?q=repo%3Aapple%2Fswift-testing%EntryPoint&type=code).
16+
[ABI.v0.EntryPoint](https://github.com/search?q=repo%3Aswiftlang%2Fswift-testing%20EntryPoint&type=code).
1717

1818
## Modified Backus-Naur form
1919

Documentation/WASI.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ See https://swift.org/CONTRIBUTORS.txt for Swift project authors
1414
because it provides instructions the reader must follow directly. -->
1515

1616
To run tests for WebAssembly, install a Swift SDK for WebAssembly by following
17-
[these instructions](https://book.swiftwasm.org/getting-started/setup-snapshot.html).
17+
[these instructions](https://book.swiftwasm.org/getting-started/setup.html).
1818

1919
Because `swift test` doesn't know what WebAssembly environment you'd like to use
2020
to run your tests, building tests and running them are two separate steps. To

Sources/Testing/Testing.docc/MigratingFromXCTest.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -397,7 +397,7 @@ Wherever possible, prefer to use Swift concurrency to validate asynchronous
397397
conditions. For example, if it's necessary to determine the result of an
398398
asynchronous Swift function, it can be awaited with `await`. For a function that
399399
takes a completion handler but which doesn't use `await`, a Swift
400-
[continuation](https://developer.apple.com/documentation/swift/withcheckedcontinuation(function:_:))
400+
[continuation](https://developer.apple.com/documentation/swift/withcheckedcontinuation(isolation:function:_:))
401401
can be used to convert the call into an `async`-compatible one.
402402

403403
Some tests, especially those that test asynchronously-delivered events, cannot

0 commit comments

Comments
 (0)