Manifest and Resource merging #591
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
First of all thanks for a great package!
I noticed this package is not using the Android manifest and resource merging provided by the Flutter toolchain. Therefore I created this PR. It makes it a little easier to use the package and you don't have to worry about compatibilty issues creeping in based ones
AndroidManifest.xmlandstyles.xml. An example is the changes for API level 35 regarding styling; etc.windowOptOutEdgeToEdgeEnforcementthat is included in this PR.@hnvn Is there a specific reason to why this isn't used?