KronosClock.getCurrentTime() behavior not clear from README
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 287
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
If I use KronosClock.getCurrentTime() and getTimeSinceLastNtpSyncMs() returns NULL, will a syncInBackground() be triggered automatically or not?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README and the KronosClock.getCurrentTime() and getTimeSinceLastNtpSyncMs() entry points. Confirm the behavior when the sync age is NULL, including whether syncInBackground() runs automatically, then document that behavior clearly in the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100