This repository was archived by the owner on Dec 4, 2017. It is now read-only.
API page cross-linking between JS/TS and Dart #1895
Labels
Comments
|
I can think of a new xref scheme that will work ~80% of the time. For now we might want to go for that and for the remaining 20% just say that no correspondence can be found. |
This was referenced Nov 4, 2016
chalin
added a commit
to IdeaBlade/angular.io
that referenced
this issue
Nov 5, 2016
- Dart non-api doc pages w/ links to API entries will now have those links translated from a TS API reference URL to a Dart API reference URL. - Created and ran a link checker to verify that all such links to API entries refer to Dart. - Fixed links to pages that have moved: - JS & Dart: `i18n` is under now `cookbook` not `guide` - Dart: testing page is now directly under guide. Contributes to angular#1895 Fixes angular#2273
kwalrath
pushed a commit
that referenced
this issue
Nov 7, 2016
- Dart non-api doc pages w/ links to API entries will now have those links translated from a TS API reference URL to a Dart API reference URL. - Created and ran a link checker to verify that all such links to API entries refer to Dart. - Fixed links to pages that have moved: - JS & Dart: `i18n` is under now `cookbook` not `guide` - Dart: testing page is now directly under guide. Contributes to #1895 Fixes #2273
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Individual API pages, like most doc pages, have a language selection dropdown at the top. Dart API pages will be supported soon (#1880, #1888) and the mapping between JS/TS and Dart API page entries is not one-to-one, and so the current cross-referencing scheme (which just changes the language but keeps the rest of the API page URL the same), needs to be replaced.
Note that this impacts JS/TS and Dart.
cc @kwalrath
The text was updated successfully, but these errors were encountered: