docs: add deprecated-api-item class to deprecated items

[ajitsinghkaler]

Fixes#31455

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Deprecated Items are not striked through

Issue Number: #31455
Deprecated Items are striked through

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[mary-poppins]

You can preview 0914863 at https://pr34088-0914863.ngbuilds.io/.

[petebacondarwin]

Thanks @ajitsinghkaler - did you check methods and other doc types too?

[petebacondarwin]

Also I think you need a space between Fixes and #31455 in the commit message.

[ajitsinghkaler]

Can I know which other methods and other doctypes I need to check

[petebacondarwin]

Look through the API pages and think about what other things might be deprecated, such as methods.
It might be helpful to search the source code in https://github.com/angular/angular/tree/master/packages to find @deprecated tags and then check that those things are being displayed correctly in the site.

[mary-poppins]

You can preview 2ce91da at https://pr34088-2ce91da.ngbuilds.io/.

[ajitsinghkaler]

@petebacondarwin As I can see I 've checked only a 13 of 233 instances there are many instances where we are not striking through the deprecated elements. I'll try to check the rest of them later. If that is okay I'm attaching the images of the failed cases. Please have a look and tell me if we even need to strike through them.

[ajitsinghkaler]

Please tell me what we need to do with them.

[petebacondarwin]

Thanks for looking into this further. When I search the code-base I see that:

• All classes, consts, interfaces, types, etc are already handled before this PR.
• All class properties and enum members are now being handled by this PR.
• Class method details are not handled. E.g.

  angular/packages/core/src/testability/testability.ts

  Line 103 in 17f7bdb

  * @deprecated pending requests are now tracked with zones.

  - see https://pr34088-2ce91da.ngbuilds.io/api/core/Testability
• Individual overloads of a method are not handled. E.g.

  angular/packages/core/src/di/injector.ts

  Line 62 in 86104b8

  * @deprecated from v4.0.0 use Type<T> or InjectionToken<T>

  - see https://pr34088-2ce91da.ngbuilds.io/api/core/Injector
• Options on decorators are not handled. E.g.

  angular/packages/core/src/metadata/directives.ts

  Line 545 in 1799f62

  * @deprecated Since 9.0.0. With Ivy, this property is no longer necessary.

  - see https://pr34088-2ce91da.ngbuilds.io/api/core/NgModule

So the templates that deal with these missing items are where we need to focus our attention.

If you want, we could mark this PR as merge, since it already improves the docs - and you could work on a 2nd PR for these other items.

[ajitsinghkaler]

Okay, we can merge this and I'll start working on the others later.

[ajitsinghkaler]

@petebacondarwin other items also work in the same way, I just have to play on the deprecated property that it and please go ahead and merge this.

[angular-automatic-lock-bot]

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.}