Q42 / Q42/Template.ComposeMultiplatform
Enable compileSafety in koinCompiler
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 15h
- Merged PRs (30d)
- 15
Description
Related to https://github.com/Q42/Template.ComposeMultiplatform/issues/84 implemented in https://github.com/Q42/Template.ComposeMultiplatform/pull/203.
Then main benefit of the Koin compiler plugin is compile-time checks for the dependency tree. When implementing support for the plugin, it turned out that it detects false-positives on iOS, but not Android, compileSafety was therefore disabled.
Scope of this ticket is to investigate how to mitigate the false-positives and possibly file an issue with the compiler plugin, and then eventually re-enable compileSafety.
Koin Compiler plugin: https://github.com/InsertKoinIO/koin-compiler-plugin
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating where compileSafety is configured in the template and review the implementation referenced by issue 84 and pull request 203. Reproduce the dependency-tree false positives on iOS while comparing Android behavior, then consult the Koin compiler plugin documentation or issue tracker. Done means the false positives are mitigated or reported and compileSafety can be re-enabled with the project checks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100