Skip to content

Commit 4c42211

Browse files
filiphsfshaza2
authored andcommitted
Fix internal links (#2715)
Some anchored internal links were broken because of changes in subtitles in the testing docs.
1 parent 86d1b07 commit 4c42211

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

src/docs/development/data-and-backend/state-mgmt/simple.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -236,7 +236,7 @@ model itself and its business logic.
236236

237237
`ChangeNotifier` is part of `flutter:foundation` and doesn't depend on
238238
any higher-level classes in Flutter. It's easily testable (you don't even need
239-
to use [widget testing](/docs/testing#widget-testing) for it). For example,
239+
to use [widget testing](/docs/testing#widget-tests) for it). For example,
240240
here's a simple unit test of `CartModel`:
241241

242242
<?code-excerpt "state_mgmt/simple/test/model_test.dart (test)"?>

src/docs/development/packages-and-plugins/developing-packages.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,14 +53,14 @@ specialized content:
5353
* `lib/hello.dart`:
5454
- The Dart code for the package.
5555
* `test/hello_test.dart`:
56-
- The [unit tests](/docs/testing#unit-testing) for the package.
56+
- The [unit tests](/docs/testing#unit-tests) for the package.
5757

5858
### Step 2: Implement the package
5959

6060
For pure Dart packages, simply add the functionality inside the main
6161
`lib/<package name>.dart` file, or in several files in the `lib` directory.
6262

63-
To test the package, add [unit tests](/docs/testing#unit-testing)
63+
To test the package, add [unit tests](/docs/testing#unit-tests)
6464
in a `test` directory.
6565

6666
For additional details on how to organize the package contents, see the

src/docs/testing/build-modes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ The Flutter tooling supports three modes when compiling your app,
77
and a headless mode for testing.
88
This doc explains the three modes and tells you when to use which.
99
For more information on headless testing, see
10-
[Unit testing.](/docs/testing#unit-testing)
10+
[Unit testing.](/docs/testing#unit-tests)
1111

1212
You choose the compilation mode depending on where you are in
1313
the development cycle. Are you debugging your code? Do you

src/docs/testing/ui-performance/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -476,7 +476,7 @@ and debugging in Flutter:
476476
[Flutter API]: {{site.api}}
477477
[UIKit]: https://developer.apple.com/documentation/uikit
478478
[MainThread]: {{site.android-dev}}/reference/android/support/annotation/MainThread
479-
[Integration testing]: /docs/testing#integration-testing
479+
[Integration testing]: /docs/testing#integration-tests
480480
[Architecture notes]: {{site.github}}/flutter/engine/wiki#architecture-notes
481481
[Widget inspector]: /docs/development/tools/inspector
482482
[Flutter Inspector talk]: https://www.youtube.com/watch?v=JIcmJNT9DNI

0 commit comments

Comments
 (0)