(jsii) --add-deprecated-warnings flag should not add warning when a non-deprecated class inherits a deprecated class

[nija-at]

🐛 Bug Report

It is acceptable for a non-deprecated class to inherit a deprecated class.
The --strip-deprecated flag correctly handles this, by not exporting the deprecated class and treating it as a private member.

However, the --add-deprecated-warnings flag does not account for this. It produces a warning when the non-deprecated subclass is used.

Example:

https://github.com/aws/aws-cdk/blob/c4ba858278bffe1a987ea8200c313f17f7f1cbe9/packages/%40aws-cdk/core/lib/bundling.ts#L251

BundlingDockerImage here is deprecated.

[nija-at]

See #3111

More examples -

https://github.com/aws/aws-cdk/blob/db63fba358a5a8cc3d252156d14ead57d2b7560d/packages/%40aws-cdk/aws-ecr-assets/lib/image-asset.ts#L58

DockerImageAssetOptions is not deprecated whereas FingerprintOptions is.

Similarly,

https://github.com/aws/aws-cdk/blob/db63fba358a5a8cc3d252156d14ead57d2b7560d/packages/%40aws-cdk/aws-s3-assets/lib/asset.ts#L17

AssetOptions is not deprecated while CopyOptions is.

[NGL321]

@otaviomacedo was this resolved with #3112?

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.