Skip to content

Finalize 4.2.2 — version bump + Navigation 3 typed entryProvider docs (#2336)#2448

Merged
arnaudgiuliani merged 1 commit into
4.2.2from
release/4.2.2-finalize
Jun 12, 2026
Merged

Finalize 4.2.2 — version bump + Navigation 3 typed entryProvider docs (#2336)#2448
arnaudgiuliani merged 1 commit into
4.2.2from
release/4.2.2-finalize

Conversation

@arnaudgiuliani

Copy link
Copy Markdown
Member

Finalizes the 4.2.2 release.

Version

Bump koinVersion 4.2.2-Alpha14.2.2.

#2336 — Navigation 3 typed entryProvider (docs)

koinEntryProvider<T>() is already generic ((T) -> NavEntry<T>). The reported mismatch happens when it's called as koinEntryProvider<Any>() but NavDisplay is typed (e.g. via a typed SceneStrategy such as rememberSupportingPaneSceneStrategy<Route>()) — the compiler then infers NavDisplay<Route> and expects (Route) -> NavEntry<Route>. The API didn't need changing; the fix is to document passing the route type:

val entryProvider = koinEntryProvider<Route>()   // matches NavDisplay<Route>
// or: val entryProvider: EntryProvider<Route> = koinEntryProvider()

Added a :::tip to the Navigation 3 reference page covering the exact error and both forms.

Verification

  • Docs + version only — no code change. ./gradlew apiCheck passes (no .api delta).

Closes #2336.

🤖 Generated with Claude Code

- Bump koinVersion 4.2.2-Alpha1 -> 4.2.2 (release).
- #2336: document that koinEntryProvider<T>() is generic and must be given the
  route type when NavDisplay is typed (e.g. via a typed SceneStrategy like
  rememberSupportingPaneSceneStrategy<Route>()). koinEntryProvider<Any>() yields
  (Any) -> NavEntry<Any>, which won't match NavDisplay<Route>; use
  koinEntryProvider<Route>() (or a typed EntryProvider<Route> variable). The API
  was already generic — this is a usage/documentation clarification.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@arnaudgiuliani arnaudgiuliani merged commit dc86ef8 into 4.2.2 Jun 12, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant