instacart / instacart/truetime-android
Why do we need to put TrueTime initialization inside of the class that extends application?
- Dominant language
- Kotlin
- Stars
- 1.5k
- Forks
- 196
- PR merge metrics
- No merged PRs in 30d
Description
I have a use case where I can't put the TrueTime initialization inside of onCreate of the class that extends application. It seems to work fine when I put it outside of this class.
Is the reason why we shouldn't place the initialization outside of this onCreate method that we'd be re-calling some sort of sync function which would exponentially increase network calls? Or is there some other sort of reason?
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the TrueTime initialization path and the Application.onCreate entry point mentioned in the issue. Determine why initialization is expected there and whether moving it causes repeated synchronization or network calls. Done means documenting the rationale and initialization constraints clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100