Decathlon / Decathlon/ara

Automatic refresh on ARA Homescreen

Open
#28 0 comments 0 reactions 0 assignees View on GitHub
Feature Request P3
Dominant language
Java
Stars
80
Forks
17
PR merge metrics
No merged PRs in 30d

Description

# Automatic refresh on ARA Homescreen

## Context

To have the most recent result, users have to click to the `Refresh` button or reload their browser tab.

## Expected
Refresh the home page of ARA every minute or so, to always have a fresh view with latest results.

Be careful, because user can go back and forth in the history of each cycle: we should not override every minute what the user is currently viewing!

Acceptance Workflow for the story:

* User loads the ARA homepage => ARA remembers the ID of the current/latest execution of each cycle
* Every minute, ARA asks latest executions to the server, and refresh each cycle view => remember the ID of the new latest executions per cycles, if changed
* User clicks [Back] several times on one cycle, to navigate the history of this cycle: the displayed execution ID of that cycle is different from the one loaded on startup or refreshed on last request
* On the next refresh, do NOT override the current navigated execution by the user (currently displayed ID is different than the latest loaded ID), but still refresh other cycles
* If user navigates with the [Next] buttons and go back to the latest execution, the displayed execution ID will be the same as the "last loaded execution ID", so on next refresh, the cycle will refresh and display the new latest execution, as expected

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by locating the ARA homepage refresh logic and the per-cycle execution-history handling, then trace how the displayed and latest execution IDs are tracked. Done means periodic updates refresh only cycles still showing their last loaded execution, while user-navigated cycles remain unchanged.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.