@petebacondarwin mind taking a look (small change)?

@petebacondarwin I updated the links in annotations to point to local anchors.

I just ran this with gulp docs and it still gives errors:

warn:    Invalid link (does not match any doc): "KeyValueChanges" - doc "properties" (member)  - from file "angular2/src/core/annotations_impl/annotations.ts"

warn:    Invalid link (does not match any doc): "KeyValueChanges" - doc "DirectiveAnnotation extends  Injectable" (class)  - from file "angular2/src/core/annotations_impl/annotations.ts"

warn:    Dangling Links Found in "partials/modules//angular2/angular2/DirectiveAnnotation extends  Injectable/index.html":
 - QueryList,
 - QueryList,
 - #onChange,
 - #onDestroy,
 - #onAllChangesDone,
 - KeyValueChanges

etc

@petebacondarwin that's related to the heritage-in-name issue that you fixed. Running against rebased master gets rid of those complaints.

I take that back. With the hash urls pointing to events, I still get dangling link issues. And if I use plain old names like {@link onDestroy}, I get "Ambiguous Link" warnings.

It seems the only combination that doesn't have errors is:

/**
 * See {@link /angular2/annotations/onChange}, {@link /angular2/annotations/onDestroy}, {@link /angular2/annotations/onCheck},
 * {@link /angular2/annotations/onInit}, {@link /angular2/annotations/onAllChangesDone} for details.
**/

I fixed the id and alias generation for members and exports and this got rid of those last problems.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}