[various] Plugin Gradle pre-Kotlin standardization#11173
[various] Plugin Gradle pre-Kotlin standardization#11173stuartmorgan-g wants to merge 9 commits intoflutter:mainfrom
Conversation
|
Version/changelog override: I'm intentionally not releasing these since the changes are no-ops in practice, and we'll be releasing all of these changes almost immediate afteward as part of #11172. |
|
@gmackall This just needs a quick rubber stamp to streamline the next PR in the conversion series. |
There was a problem hiding this comment.
Code Review
This pull request performs a broad standardization of Groovy Gradle build files across numerous packages. The changes apply more modern Gradle DSL syntax, such as using double quotes, parentheses for method calls, the = for assignments, and updating properties like minSdkVersion to minSdk and lintOptions to lint, in preparation for a migration to Kotlin Gradle files.
The standardization appears to be incomplete for packages/local_auth/local_auth_android/android/build.gradle. This file still contains older syntax (e.g., single quotes for group and version, and method calls without parentheses) that has been updated in other files in this PR. Applying the standardization consistently to all files would better achieve the PR's stated goal.
local_auth wasn't supposed to be included, to avoid conflicts with #11169. Reverted. |
As a precursor to converting plugins to use Kotlin Gradle build files in #11172, this does some final standardization of the Groovy versions:
"instead of'on more lines.(...)and=in places where it's optional, instead of just a space.minSdkinstead ofminSdkVersion.This is being done as a precursor PR because I noticed that the files are mostly right on the cusp of being similar enough for git to think they are renames with changes rather than deletion and addition; some are ending up one way, and some the other. Since renames with changes make blame much more useful, I'd like to make the files more similar so that hopefully almost all of them will end up as renames with changes in that PR.
Pre-Review Checklist
[shared_preferences]///).Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2