Adding tooling links using new /to/ format
#10765
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
parlough
requested review from
sfshaza2,
atsansone,
khanhnwin,
domesticmouse and
MaryaBelanger
as code owners
|
Visit the preview URL for this PR (updated for commit 0a69079): https://flutter-docs-prod--pr10765-feat-10363-ovj4d2l9.web.app |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The links added here will be used from various locations that need consistently functional links that are sometimes manually copy and pasted. The current set includes links the
fluttertool, DevTools, the VS Code plugin(s), the Flutter framework, as well as some surrounding documentation.It's particularly important to have these links for areas relying on fragments, as those redirects can't happen on the server side, and developers may continue to run SDKs or tools with old links long after their destination needs to change.
After this PR,
/go/<design-doc>should only be used for design docs going forward. Only one item long, top-level redirects such asdocs.flutter.dev/<top-level>should also be avoided from now on.Once this lands, I will update the tools where necessary and land documentation in the
flutter/flutterrepository that ensures this format of link is considered.Contributes to #10363