[local_auth] Convert to Kotlin gradle for the plugin build files by stuartmorgan-g · Pull Request #11169 · flutter/packages
Following up from #11127, this is the initial example of converting a plugin build, rather than an example app build, to Kotlin gradle.
This conversion was done manually, but closely referencing the current plugin template files. It differs mostly in not having the parts that are specific to the use of Kotlin source files, since local_auth is still Java-only. Later (when we start adopting Kotlin Pigeon generation everywhere, for instance) some of the diffs relative to the template files will go away.
Unlike #11127 this did not require tool changes, as it turns out that the previous changes were enough to handle these files, but I did add more tests. As with #11127 I did not attempt to comprehensively duplicate all Groovy tests, since we should be able to relatively quickly convert everything in the repo, and then pull out the Groovy support and update all the tests to Kotlin.
Note that this does not convert the plugin's example app to Kotlin gradle, only the plugin itself. The example app for plugins are non-trivial enough (due to native tests) that they should be converted separately. This has the bonus effect of validating that the plugin migration didn't require any changes in the client app.
Part of flutter/flutter#176065
Pre-Review Checklist
- I read the Contributor Guide and followed the process outlined there for submitting PRs.
- I read the Tree Hygiene page, which explains my responsibilities.
- I read and followed the relevant style guides and ran the auto-formatter.
- I signed the CLA.
- The title of the PR starts with the name of the package surrounded by square brackets, e.g.
[shared_preferences] - I linked to at least one issue that this PR fixes in the description above.
- I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under1.
- I updated/added any relevant documentation (doc comments with
///). - I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under1.
- All existing and new tests are passing.