Fix some discrepancies in @Deprecated handling in Metalava
Previously, Metalava had some inconsistencies in the handling of deprecated status which lead to some inconsistencies in the API signature files. This change fixes those signatures. * `onGetLayoutInflater` was removed because the code to determine whether a method is elided from the signature files because it matches an overridden method will only elide a method if it has the same deprecated status as the overridden method. However, in some cases it would not take into account that the method, while not explicitly deprecated was a member of a deprecated class. That meant that `onGetLayoutInflater` was kept in the API signature file when it should not have been. That issue is fixed in this topic and so this change removes it. * `setPackagesSuspended` had an `@Deprecated` annotation added to it because while the API signature writing was supposed to add an `@Deprecated` annotation for a method that was explicitly deprecated or a member of a deprecated class in some cases the latter was ignored. That issue is fixed in this topic and so this change adds the previously missing `@Deprecated` annotation. Bug: 315206833 Test: m checkapi Change-Id: I0ef23d32c5b5b11f964aeb93c2bb0346d75cea83
Loading
Please register or sign in to comment