Update Router API documentation#37980
Conversation
|
You can preview 8e4b631 at https://pr37980-8e4b631.ngbuilds.io/. |
|
You can preview 049a6fd at https://pr37980-049a6fd.ngbuilds.io/. |
|
You can preview 8e06739 at https://pr37980-8e06739.ngbuilds.io/. |
|
You can preview f32977e at https://pr37980-f32977e.ngbuilds.io/. |
|
You can preview 924df2e at https://pr37980-924df2e.ngbuilds.io/. |
|
You can preview ec00597 at https://pr37980-ec00597.ngbuilds.io/. |
|
You can preview abbfa49 at https://pr37980-abbfa49.ngbuilds.io/. |
|
You can preview 4bbd262 at https://pr37980-4bbd262.ngbuilds.io/. |
|
I don't know why this PR is requesting public-api approvers because AFAICT it doesn't touch anything there. @atscott once you approve this PR feel free to ping me for global approval |
|
@jelbourn it is because of this line here https://github.com/angular/angular/pull/37980/files?file-filters%5B%5D=.ts#diff-d4a2188410be78a020e88630cdafa20dL151 |
c43ff61 to
7ee48c6
Compare
|
You can preview 7ee48c6 at https://pr37980-7ee48c6.ngbuilds.io/. |
|
You can preview 3efead9 at https://pr37980-3efead9.ngbuilds.io/. |
jelbourn
left a comment
There was a problem hiding this comment.
LGTM - using global-approvers because the public API change is removing a deprecation marker that wasn't supposed to be on that symbol in the first place
Reviewed-for: global-approvers
3efead9 to
7906e0f
Compare
Edit descriptions, usage examples, and add links to be complete and consistent with API reference doc style
7906e0f to
ce88f29
Compare
|
You can preview ce88f29 at https://pr37980-ce88f29.ngbuilds.io/. |
Edit descriptions, usage examples, and add links to be complete and consistent with API reference doc style PR Close #37980
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Edit descriptions, usage examples, and add links to be complete and consistent with API reference doc style PR Close angular#37980


Edit descriptions, usage examples, and add links to be complete and consistent with API reference doc style
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Router API docs are incomplete and do not follow current standards.
Does not use terminology consistently or in accordance with guide usage.
Issue Number: N/A
What is the new behavior?
Adds links to guides and among members, adds, restructures, and edits descriptions of public members.
Does this PR introduce a breaking change?