Skip to content

F-115: Hilt Path A engine fix + NiA dogfood docs - #232

Merged
stepango merged 1 commit into
v2from
forma/F-115-hilt-path-a
Jul 30, 2026
Merged

F-115: Hilt Path A engine fix + NiA dogfood docs#232
stepango merged 1 commit into
v2from
forma/F-115-hilt-path-a

Conversation

@stepango

Copy link
Copy Markdown
Collaborator

Summary

  • Engine: applyTargetPlugins accepts optional configurationFeatures and forwards it when applying type-owned companion deps. Wired on impl / androidApp / androidUtil / uiLibrary / library / androidBinary.
  • Why: Hilt Path A (targetPlugin(..., dependencies = hilt + compiler.ksp)) failed with Configuration with name 'ksp' not found because companion deps bypassed the host DSL’s KSP bootstrap.
  • Dogfood (external, not in this repo): /Users/claw/work/nowinandroid-forma/forma-spike — Path A hiltImpl/hiltApp/hiltAndroidUtil/hiltBinary, @HiltAndroidApp on binary, features on Hilt VMs, no implimpl.
  • Docs: DOGFOOD-NIA.md phase C Hilt + findings F12/F13; TICKETS/PROGRESS/TARGET-PLUGINS.

Verify

  • plugins/ ./gradlew :deps:test publishAllToMavenLocal -PformaLocalVersion=0.1.3-NIA → BUILD SUCCESSFUL
  • external spike ./gradlew :binary:assembleDebug → BUILD SUCCESSFUL (242 tasks; Hilt aggregate/compile green); APK ~9.4MB

Ticket

F-115 still in_progress — next: Room / more features. F-094 still blocked human.

Forward processorConfigurationFeatures from host DSLs into applyTargetPlugins
so targetPlugin companion .ksp deps create the ksp configuration (Hilt Path A).
Document green external spike (hiltImpl/hiltApp/hiltAndroidUtil/hiltBinary).
@stepango
stepango merged commit 63790be into v2 Jul 30, 2026
8 checks passed
@stepango
stepango deleted the forma/F-115-hilt-path-a branch July 30, 2026 05:39
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