[AndroidManifest.xml] Determine which attributes to expose in Mono.Android. #9092
Assignees
Labels
Area: Mono.Android
Issues with the Android API binding (Mono.Android.dll).
enhancement
Proposed change to current functionality.
Milestone
Comments
jpobst
added
the
Area: Mono.Android
jpobst
added
enhancement
jonathanpeppers
pushed a commit
that referenced
this issue
Aug 6, 2024
…9096) Fixes: #9092 Context: 3ab74db Previously in commit 3ab74db, we created a process for automatically determining the possible attributes for elements in `AndroidManifest.xml` and generating the `[Application]`, `[Activity]`, etc. attributes within `Mono.Android.dll` for users to consume. At the time, we merely created the process, but did not use it to expose any new attributes that have been added in previous Android API levels that we never exposed. This commit exposes all Google-documented manifest attributes for the elements we support. The undocumented manifest attributes were moved around in the file to a section denoted as "undocumented".
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Context: #8272
Previously, we created a process for automatically determining the possible attributes for elements in
AndroidManifest.xmland generating theMono.Android[Application],[Activity], etc. attributes for users to consume. At the time, we merely created the process, but did not use it to expose any new attributes that have been added in previous Android API levels that we never added.We should create a list of all attributes we are missing, and then determine which of them we want to expose for users. Note that our process that goes directly to the source finds many attributes that Android does not publicly document. Thus we will need to evaluate each attribute to determine if we want to expose it.
The text was updated successfully, but these errors were encountered: