Skip to content

Additional API-30 deprecations #602

@jpobst

Description

@jpobst

From #509:

Additional/related changes:

We should also [Obsolete(error:true)] all of the nested InterfaceConsts types, such as Android.OS.Binder.InterfaceConsts.


For API-30, we should [Obsolete(error:true)] "interface proxy" types such as Android.Content.ComponentCallbacks2, which contains fields for the android.content.ComponentCallbacks2 interface and lives "alongside" the Android.Content.IComponentCallbacks2 interface. Additionally, all of these fields should be moved into the appropriate C# interface, e.g. every field within Android.Content.ComponentCallbacks2 should reside in the Android.Content.IComponentCallbacks2 type, using C#8 default interface members.

^^ This was done in #600. We did not make them an error to allow a smoother migration path, as the new members would not be available in API-29.


We should also [Obsolete(error:true)] all members which are already [Obsolete].

^^ I'm not aware of any additional members that need to be changed.

Metadata

Metadata

Assignees

Labels

enhancementProposed change to current functionalitygeneratorIssues binding a Java library (generator, class-parse, etc.)

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions