organize and update deprecation summary - #26733
jenniferfell wants to merge 5 commits into
Conversation
|
WIP: Still gathering information and related links. Not ready for review. |
|
You can preview f7af4f4 at https://pr26733-f7af4f4.ngbuilds.io/. |
|
note to self: add https://github.com/angular/quickstart/blob/master/README.md |
|
Also related for follow-up: #22640 |
f7af4f4 to
dda7c9e
Compare
|
You can preview dda7c9e at https://pr26733-dda7c9e.ngbuilds.io/. |
|
You can preview 9c2ffdb at https://pr26733-9c2ffdb.ngbuilds.io/. |
9c2ffdb to
4b9a8ba
Compare
|
You can preview 4b9a8ba at https://pr26733-4b9a8ba.ngbuilds.io/. |
4b9a8ba to
baea845
Compare
c1a3865 to
d764b02
Compare
|
The latest commit has the loadChildren changes suggested by @trotyl. Keeping as separate commit until I hear back from engineering. The latest commit also has a fix to misspelling of "Compilation." |
|
You can preview eb4c9b5 at https://pr26733-eb4c9b5.ngbuilds.io/. |
e4bb8f8 to
8a59f67
Compare
Co-Authored-By: jenniferfell <[email protected]>
8a59f67 to
23fa8e2
Compare
|
You can preview 19d03e0 at https://pr26733-19d03e0.ngbuilds.io/. |
IgorMinar
left a comment
There was a problem hiding this comment.
this looks good now! I still have a few nits (H4s -> H3s, and add a bit more space in front of each H3 to visually separate the items in the doc) but those changes can be done in a follow up PR.
|
|
||
|
|
||
|
|
||
| #### @angular/common |
There was a problem hiding this comment.
are these intentionally H4s? The consequence of H4 is that they don't show up in TOC which is a shame. could this be made H3s in a followup PR? thanks!
Co-Authored-By: jenniferfell <[email protected]> PR Close #26733
Co-Authored-By: jenniferfell <[email protected]> PR Close angular#26733
|
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. |
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?
There is no consolidated list of deprecated features, with version deprecated and replacement info/link. The API List can be filtered to show only deprecated APIs. Deprecated APIs are shown with strikethrough in search, API List, and package overview pages.
Issue Number: #26585
What is the new behavior?
Deprecated APIs and features are summarized in one place, with link to other places as needed.
Easy to tell when something was deprecated (or when it will be removed).
Does this PR introduce a breaking change?
Other information