[analysis server] Fix links in implementation docs
Change-Id: Ie40111a6bfed4a6f088f1e7bd3f365aa060a1b0c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/393700 Reviewed-by: Samuel Rawlins <srawlins@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com>
This commit is contained in:
committed by
Commit Queue
parent
53bad058b1
commit
b47128dd64
@@ -10,11 +10,11 @@ distinguish between three kinds of code editing features:
|
||||
|
||||
- a [quick assist](quick_assist.md) is a code edit that is both local in scope
|
||||
and doesn't require any user input. They are available when the selection is
|
||||
within the assist's [available range][].
|
||||
within the assist's [available range](#choosing-an-available-range).
|
||||
|
||||
- a [refactoring]() is a code edit that is either non-local in scope or that
|
||||
requires user input. They are available when the selection is within the
|
||||
assist's [available range][].
|
||||
assist's [available range](#choosing-an-available-range).
|
||||
|
||||
## Scope
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ they are a way of allowing a package author to specify API-specific quick fixes.
|
||||
|
||||
Before you read this you should be familiar with both
|
||||
- [Writing a quick fix](quick_fix.md), and
|
||||
- [Data-driven Fixes](https://github.com/flutter/flutter/wiki/Data-driven-Fixes).
|
||||
- [Data-driven Fixes](https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md).
|
||||
|
||||
## How data-driven fixes work
|
||||
|
||||
@@ -78,7 +78,7 @@ you would instead modify something that already exists.
|
||||
The first step is to design the changes to the data-file format that will allow
|
||||
users to specify the change. Follow the design principles outlined in the
|
||||
Overview in
|
||||
[Data-driven Fixes](https://github.com/flutter/flutter/wiki/Data-driven-Fixes).
|
||||
[Data-driven Fixes](https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md).
|
||||
|
||||
In addition, look at the existing changes to ensure that a new kind of change is
|
||||
required. It might make more sense to extend an existing change rather than to
|
||||
|
||||
Reference in New Issue
Block a user