Nullable `@InjectedParam` with null value causes the subsequents receive the wrong value.

Open
#53 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
kotlin
Domain
compilers

Research direction

Start with the attached Koin_InjectedParam_Explanation.md to understand the nullable parameter-cursor failure, then trace the Koin compiler plugin code that handles @InjectedParam values and parametersOf. Reproduce a nullable parameter followed by a repeated type, and consider the issue resolved when the cursor advances past null and each subsequent parameter receives its intended value.

Written by the indexing model from the issue text.

Description

When a nullable @InjectedParam is passed null at runtime, Koin's parameter cursor stalls at that position. Any subsequent @InjectedParam whose type also appears earlier in the parametersOf array will silently receive the wrong value.

Below is the analytic in details.
Koin_InjectedParam_Explanation.md

Dominant language
Kotlin
Stars
82
Forks
15
Avg merge
1m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InsertKoinIO/koin-compiler-plugin

All issues in InsertKoinIO/koin-compiler-plugin

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.