adobe / adobe/aepsdk-core-android
[discussion] validation of core exposed services/shared instances
Open
defer
discussion
- Dominant language
- Kotlin
- Stars
- 17
- Forks
- 30
- Avg merge
- 4h 12m
- Merged PRs (30d)
- 4
Description
If core exposed services/shared instances are not initialized correctly or are not ready to use, should we block the registration of extensions? Or we should let the extension make the validation when registering itself to Eventhub and decide how to handle the other logic.
Contributor guide
Research direction
Start by tracing initialization of the core exposed services and shared instances, then follow extension registration through Eventhub. Determine whether registration should be blocked when core services are unavailable or whether each extension validates them, and document the chosen behavior and handling of failure cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100