cortinico / kotlin-android-template Goto Github PK

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency androidx.test:runner to v1.5.2
• Update dependency org.jetbrains.kotlin:kotlin-gradle-plugin to v1.9.24
• Update gradle/wrapper-validation-action action to v3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

🐛 Describe the bug

⚠️ Current behavior

✅ Expected behavior

💣 Steps to reproduce

📷 Screenshots

📱 Tech info

• Device:
• OS:
• Library/App version:

I just bumped into the Jetbrains template for IntelliJ plugins (https://github.com/JetBrains/intellij-platform-plugin-template#getting-started). They have a Github Action that replaces the template values with values from the fork repo. I think it'd be a great addition to this template: it'll make sure users don't forget to remove the default value and save some manual configuration.

I'm not sure I'll have a lot of time to work on this but if someone feels like investigating Github Actions, I think that'd be a good fit.

🐛 Describe the bug

Clicking the detekt link in the README opens https://github.com/arturbosch/detekt.

✅ Expected behavior

Clicking the detekt link in the README should open https://github.com/detekt/detekt because detekt has been moved from https://github.com/arturbosch/detekt

⚠️ Is your feature request related to a problem? Please describe

Nowdays it's recommended to use compose BOM versioning instead of hard references to using a specific version for all compose libraries. See https://developer.android.com/jetpack/compose/bom

💡 Describe the solution you'd like

A solution with version catalogs is explained at https://developer.android.com/jetpack/compose/bom#does_the_bom_work_with_version_catalogs. At work I am not using version catalogs yet so I can't get it working with a <2min PR 😢

🤚 Do you want to develop this feature yourself?

• Yes
• No (Note: At least not right now)

It would be nice to change the name of the initial branch from master to main.

⚠️ Is your feature request related to a problem? Please describe

No clue why there are so many directories and what they do.

💡 Describe the solution you'd like

Add directory descriptions to readme or docs.

🤚 Do you want to develop this feature yourself?

• Yes
• No

⚠️ Is your feature request related to a problem? Please describe

When getting started with the template and the first build new directories that are typically ignored for version control are not successfully ignored. (eg. various .xml files that relate to IDE config)

💡 Describe the solution you'd like

A more comprehensive .gitignore could be used such as this one could be beneficial to this template as it is one less thing to worry about.

🤚 Do you want to develop this feature yourself?

• Yes
• No

Should I add them inside buildSrc folder?

plugins {
    `kotlin-dsl`
}

repositories {
    google()
    mavenCentral()
}

dependencies {
    implementation(group = "com.android.tools.build", name = "gradle", version = "7.0.1")
    implementation(kotlin(module = "gradle-plugin", version = "1.5.30"))
    implementation(group = "com.google.dagger", name = "hilt-android-gradle-plugin", version = "2.38.1")
    implementation(group = "androidx.navigation", name = "navigation-safe-args-gradle-plugin", version = "2.3.5")
}

Thanks

⚠️ Is your feature request related to a problem? Please describe

Add support for code coverage

💡 Describe the solution you'd like

Ideally we could setup jacoco + codecov to have an automated test report after every push/pr.

🤚 Do you want to develop this feature yourself?

• Yes
• No

This feature is up for grab

⚠️ Is your feature request related to a problem? Please describe

In real project, we often have build flavor.

💡 Describe the solution you'd like

Add example of flavor staging and production in build.gradle.kts

🤚 Do you want to develop this feature yourself?

• Yes
• No
  (Sorry, I'm not so familiar with Kotlin Gradle script).

🐛 Describe the bug

The Template App gets crashed when we click on compute button w/o entering any number in the EditText.

⚠️ Current behaviour

The Template App gets crashed when we click on compute button w/o entering any number in the EditText.

✅ Expected behaviour

The app should not get crashed.

💣 Steps to reproduce

1. Run the App.
2. Don't Enter any text in EditText.
3. Click compute button.
4. App gets crashed.

📷 Screenshots

📱 Tech info

• Device: Google Pixel 3
• OS: 10.0.0
• Library/App version: 1.0.0

The Dependencies.kt mentioned in the README does not exist.

Dependencies are centralized inside the Dependencies.kt file in the buildSrc folder. This provides convenient auto-completion when writing your gradle files.

⚠️ Is your feature request related to a problem? Please describe

ActivityTestRule inside the espresso test case is deprecated .

💡 Describe the solution you'd like

I believe we could add JUnit KTX extension library , and then:

@get:Rule val activityScenarioRule = activityScenarioRule<MainActivity>()

🤚 Do you want to develop this feature yourself?

• Yes
• No

⚠️ Is your feature request related to a problem? Please describe

One of the use cases of this repo is to build sample projects for submitting bug reports. This has been a painpoint since my development directory is full of different sample projects, and often I need to upgrade to the latest version of the tools I used.

💡 Describe the solution you'd like

Add a flavor for using Jetpack Compose. As Compose still evolves rapidly, and I have been struggling a lot to keep a repo up-to-date with all the build setup.
The flavor could be a subproject or a different branch: I am open to any suggestion.

🤚 Do you want to develop this feature yourself?

• Yes
• No

⚠️ Is your feature request related to a problem? Please describe

I have just seen this repo and thought auto pr review bot could help developers productivity

💡 Describe the solution you'd like

as static analysis tools already integrated we could integrate danger to use static analysis tools output as a pr review.

🤚 Do you want to develop this feature yourself?

• Yes
• No