Android practice
active 2023-12-27 → 2025-05-12 (UTC)
Complete coverage26,333 / 26,333 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-16 (UTC)
Events
32
Pushes
9
Pull requests
0
Issues
21
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 503 days from 2023-12-27 to 2025-05-12. Pushes: 9 total, peak 2 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 21 total, peak 20 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| CheoR | 30 | 9 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#22CheoR2024-01-02 19:50Redo some of the compnents with Relay. E.g. Card variants https://developer.android.com/jetpack/compose/tooling/relay/content-parameters-advanced
- Issue#21CheoR2023-12-30 20:14Feature: Display bottom appbar actions when user clicks on card Scenario: User clicks on card to show action for that card Given a user wants to see allowable actions for given item When they click on the card for the item Then the bottom navigation appbar turns into bottom appbar actions
- Issue#20CheoR2023-12-30 20:14Feature: Display bottom appbar actions when user clicks on card Scenario: User clicks on card to show action for that card Given a user wants to see allowable actions for given box When they click on the card for the box Then the bottom navigation appbar turns into bottom appbar actions
- Issue#19CheoR2023-12-30 20:14Feature: Display bottom appbar actions when user clicks on card Scenario: User clicks on card to show action for that card Given a user wants to see allowable actions for given collection When they click on the card for the collection Then the bottom navigation appbar turns into bottom appbar actions
- Issue#18CheoR2023-12-30 20:14Feature: Display Dialogs when Deleting Collections, Boxes, and Items Tests Scenario: Displaying dialog when deleting an item Given a user wants to delete an existing item When they choose to delete the item Then a dialog should appear showing the item's value
- Issue#17CheoR2023-12-30 20:14Feature: Display Dialogs when Deleting Collections, Boxes, and Items Tests Scenario: Displaying dialog when deleting a box Given a user wants to delete an existing box When they choose to delete the box Then a dialog should appear showing the total number of items in the box and the total value of items in the box
- Issue#16CheoR2023-12-30 20:14Feature: Display Dialogs when Deleting Collections, Boxes, and Items Tests Scenario: Displaying dialog when deleting a collection Given a user wants to delete an existing collection When they choose to delete the collection Then a dialog should appear showing the total number of boxes in the collection, the total value of items in the boxes, the total number of items in the box, and the total value of items in the box
- Issue#15CheoR2023-12-30 20:14Feature: Bottom App Bar Navigation Tests Scenario: Navigating between screens using the bottom app bar Given the user is on the home screen When they tap on the bottom app bar to navigate to another screen Then the app should navigate to the selected screen successfully
- Issue#13CheoR2023-12-30 20:14Feature: Deleting Items, Boxes, and Collections Tests Scenario: Deleting a box Given a user wants to delete an existing box When they confirm the deletion Then the box should be removed successfully
- Issue#12CheoR2023-12-30 20:13Feature: Deleting Items, Boxes, and Collections Tests Scenario: Deleting an item Given a user wants to delete an existing item When they confirm the deletion Then the item should be removed successfully
- Issue#11CheoR2023-12-30 20:13Feature: Editing Items, Boxes, and Collections Tests Scenario: Editing a collection Given a user wants to edit an existing collection When they modify valid collection details Then the collection should be updated successfully
- Issue#10CheoR2023-12-30 20:13Feature: Editing Items, Boxes, and Collections Tests Scenario: Editing a box Given a user wants to edit an existing box When they modify valid box details Then the box should be updated successfully
- Issue#9CheoR2023-12-30 20:13Feature: Editing Items, Boxes, and Collections Tests Scenario: Editing an item Given a user wants to edit an existing item When they modify valid item details Then the item should be updated successfully
- Issue#8CheoR2023-12-30 20:13Feature: Adding New Items, Boxes, and Collections Tests Scenario: Adding a new collection Given a user wants to add a new collection When they provide valid collection details Then a new collection should be added successfully
- Issue#7CheoR2023-12-30 20:13Feature: Adding New Items, Boxes, and Collections Tests Scenario: Adding a new box Given a user wants to add a new box When they provide valid box details Then a new box should be added successfully
- Issue#6CheoR2023-12-30 20:13Feature: Adding New Items, Boxes, and Collections Tests Scenario: Adding a new item Given a user wants to add a new item When they provide valid item details Then a new item should be added successfully
- Issue#5CheoR2023-12-30 20:13Feature: User Authentication Tests Scenario: User logout Given a logged-in user When they choose to log out Then they should be logged out successfully
- Issue#4CheoR2023-12-30 20:13Feature: User Authentication Tests Scenario: User login failure Given an unregistered user When they provide invalid login credentials Then login should fail with appropriate error messages
- Issue#3CheoR2023-12-30 20:13Feature: User Authentication Tests Scenario: User login success Given a registered user When they provide valid login credentials Then they should be logged in successfully
- Issue#2CheoR2023-12-30 20:13Feature: User Authentication Tests Scenario: User registration failure Given a user wants to register When they provide invalid registration details Then registration should fail with appropriate error messages
- Issue#1CheoR2023-12-30 20:12Feature: User Authentication Tests Scenario: User registration success Given a user wants to register When they provide valid registration details Then their account should be created successfully
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.