Feature Request P3
Status Update
No update yet.
Comments
an...@google.com
Android Bug Scrub: This issue has been open for 270 days or pinged by blunderbuss 5 times with no updates. As a result, this issue looks stale to us.
Please help us out! If you are planning to work on this issue within the next year, please reply indicating the timeline you intend to complete the work and remove the "Android Blintz Close Candidate" hotlist. If it is expected for this issue to take multiple years to resolve, please add it to the android_icebox hotlist (https://b.corp.google.com/hotlists/4240 )
Stale issues that aren't removed from the "Android Blintz Close Candidate" will be closed in 7 days, so if you think this should be closed there's no need to do anything. For more information please see go/android-blintz.
If you are not the assignee of this bug, and feel this issue needs to be escalated, please email the components default assignee with the bug number, and what you'd like to escalate.
Please help us out! If you are planning to work on this issue within the next year, please reply indicating the timeline you intend to complete the work and remove the "Android Blintz Close Candidate" hotlist. If it is expected for this issue to take multiple years to resolve, please add it to the android_icebox hotlist (
Stale issues that aren't removed from the "Android Blintz Close Candidate" will be closed in 7 days, so if you think this should be closed there's no need to do anything. For more information please see go/android-blintz.
If you are not the assignee of this bug, and feel this issue needs to be escalated, please email the components default assignee with the bug number, and what you'd like to escalate.
au...@google.com
This is still valid, keeping it open.
al...@google.com
Leaving assigned to Tor in case he wants to implement / reassign, but I'm also happy to sponsor this as a bounty.
Sponsor: alanv@
Estimated workload: 2 days
Technologies: Lint, annotations
Sponsor: alanv@
Estimated workload: 2 days
Technologies: Lint, annotations
an...@google.com
Android Bug Scrub: This issue has been open for 270 days or pinged by blunderbuss 5 times with no updates. As a result, this issue looks stale to us.
Please help us out! If you are planning to work on this issue within the next year, please reply indicating the timeline you intend to complete the work and remove the "Android Blintz Close Candidate" hotlist. If it is expected for this issue to take multiple years to resolve, please add it to the android_icebox hotlist (https://b.corp.google.com/hotlists/4240 )
Stale issues that aren't removed from the "Android Blintz Close Candidate" will be closed in 7 days, so if you think this should be closed there's no need to do anything. For more information please see go/android-blintz.
If you are not the assignee of this bug, and feel this issue needs to be escalated, please email the components default assignee with the bug number, and what you'd like to escalate.
Please help us out! If you are planning to work on this issue within the next year, please reply indicating the timeline you intend to complete the work and remove the "Android Blintz Close Candidate" hotlist. If it is expected for this issue to take multiple years to resolve, please add it to the android_icebox hotlist (
Stale issues that aren't removed from the "Android Blintz Close Candidate" will be closed in 7 days, so if you think this should be closed there's no need to do anything. For more information please see go/android-blintz.
If you are not the assignee of this bug, and feel this issue needs to be escalated, please email the components default assignee with the bug number, and what you'd like to escalate.
an...@google.com
Android Issue Scrub: This issue has been open for 270 days or pinged by blunderbuss 5 times with no updates. As a result, this issue looks stale to us.
Please help us out! If you are planning to work on this issue within the next year, please reply indicating the timeline you intend to complete the work and remove the "Android Blintz Close Candidate" hotlist. If it is expected for this issue to take multiple years to resolve, please add it to either the android_icebox (https://b.corp.google.com/hotlists/4240 ) or Android Blintz Ignore (https://b.corp.google.com/hotlists/2808047 ) hotlist.
Stale issues that aren't removed from the "Android Blintz Close Candidate" will be closed in 7 days, so if you think this should be closed there's no need to do anything. For more information please see go/android-blintz.
If you are not the assignee of this issue, and feel this issue needs to be escalated, please email the components default assignee with the issue number, and what you'd like to escalate.
Please help us out! If you are planning to work on this issue within the next year, please reply indicating the timeline you intend to complete the work and remove the "Android Blintz Close Candidate" hotlist. If it is expected for this issue to take multiple years to resolve, please add it to either the android_icebox (
Stale issues that aren't removed from the "Android Blintz Close Candidate" will be closed in 7 days, so if you think this should be closed there's no need to do anything. For more information please see go/android-blintz.
If you are not the assignee of this issue, and feel this issue needs to be escalated, please email the components default assignee with the issue number, and what you'd like to escalate.
al...@google.com
em...@google.com
If this is still open, it might be worth giving this a go for the next annotation release
al...@google.com
The platform recently added CurrentTimeMillisLong, CurrentTimeSecondsLong, DurationMillisLong, and ElapsedRealtimeLong. At the very least, we should port those to Jetpack.
al...@google.com
Moving back to the bounty list! I am still sponsoring.
Description
We have a myriad of APIs in both the framework and support library that deal in time but with units whose enforcement is only done via parameter naming hints (i.e., delayMillis) and/or documentation. These annotations would disambiguate for static analysis purposes to prevent bugs.
This would require that APIs like TimeUnit and java.time.* could be annotated (or hardcoded into lint) as they are the primary means of conversion between these units.
Some APIs are in the shape of `foo(long, TimeUnit)` which would also require analysis that when you have a @Millis long you are passing MILLISECONDS for a TimeUnit parameter that is immediately after.
It's worth noting that future platform APIs should be using java.time.Duration and friends instead of int/long.
Came up in ag/3774440