airbnb / airbnb/DeepLinkDispatch

Add @DeepLinkModuleRegistry marker annotation to generated registries

Open
#348 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
4.4k
Forks
414
PR merge metrics
No merged PRs in 30d

Description

Would it be possible to add a marker annotation (suggesting @DeepLinkModuleRegistry) to the registry types which are generated from @DeepLinkModule annotated types (I'd be happy to help contribute the change)? My use case is I want to be able to aggregate instances of the generated registries from multiple gradle modules into a single Dagger Multibinding so they can be injected into my DeepLinkDelegate. However, I want to automate the Dagger Multibinding contribution code with my own annotation processor, so I need an annotation on the generated registries to trigger a kapt round. Using KSP to initiate code generation from arbitrary symbols is not currently an option for me.

Contributor guide

Open the contributing guide

Research direction

Start by locating the annotation-processing entry point for @DeepLinkModule and the generation of registry types. Add the requested @DeepLinkModuleRegistry marker to generated registries, then verify that the result supports the described kapt round and Dagger multibinding workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.