@@ -27,9 +27,13 @@ else {
27
27
By default, [ ` reportIssue ` ] ( < doc:reportIssue(_:fileID:filePath:line:column:) > ) will trigger an
28
28
unobtrusive, purple runtime warning when running your app in Xcode (simulator and device):
29
29
30
- ![ A purple runtime warning in Xcode showing that an issue has been reported.] ( runtime-warning )
30
+ <picture >
31
+ <source media =" (prefers-color-scheme: dark) " srcset =" Sources/IssueReporting/Resources/runtime-warning~dark.png " >
32
+ <source media =" (prefers-color-scheme: light) " srcset =" Sources/IssueReporting/Resources/runtime-warning.png " >
33
+ <img alt =" A purple runtime warning in Xcode showing that an issue has been reported. " src =" Sources/IssueReporting/Resources/runtime-warning.png " >
34
+ </picture >
31
35
32
- This provides a very visible way to see when an issue has occured in your application without
36
+ This provides a very visible way to see when an issue has occurred in your application without
33
37
stopping the app's execution and interrupting your workflow.
34
38
35
39
The [ ` reportIssue ` ] ( < doc:reportIssue(_:fileID:filePath:line:column:) > ) tool can also be customized
@@ -43,7 +47,11 @@ framework), all reported issues become _test failures_. This helps you get test
43
47
problematic code paths are not executed, and makes it possible to build testing tools for libraries
44
48
that ship in the same target as the library itself.
45
49
46
- // TODO: test failure image
50
+ <picture >
51
+ <source media =" (prefers-color-scheme: dark) " srcset =" Sources/IssueReporting/Resources/test-failure~dark.png " >
52
+ <source media =" (prefers-color-scheme: light) " srcset =" Sources/IssueReporting/Resources/test-failure.png " >
53
+ <img alt =" A purple runtime warning in Xcode showing that an issue has been reported. " src =" Sources/IssueReporting/Resources/test-failure.png " >
54
+ </picture >
47
55
48
56
// TODO: link to get started article
49
57
0 commit comments