Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: render-oss/cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.5.0
Choose a base ref
...
head repository: render-oss/cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.6.0
Choose a head ref
  • 1 commit
  • 6 files changed
  • 1 contributor

Commits on Dec 8, 2025

  1. [CAP-7450] Implement paginated infinite scroll on CLI logs viewer (#243) 

    * Move log limit constant into shared package

Might be overkill, but this will protect us against documentation inconsistency if we decide to change this value in the backend.

* [CAP-7450] Implement paginated infinite scroll on CLI logs viewer

Implements automatic pagination for the logs viewer that fetches additional logs when users scroll to the boundaries of the fetched log data. The initial log request continues to respect the `limit` flag, but subsequent requests (triggered by scrolling) are auto-paginated with a 1000-log limit. Subsequent requests are also 'silent' and do not display the loading spinner.

Logs always display oldest to newest regardless of "direction", consistent with the existing implementation. ("Direction" only affects which end of the fetched set appears first in the viewport.)

* [CAP-7450] Support scrolling up immediately after initial log load

Existing logic only fetches logs when the viewport has shifted to a boundary of the fetched set. This is valuable because it prevents us from fetching older logs until the user requests it; however it also prevents the user from immediately scrolling up after the initial log fetch because the viewport has not shifted. This commit manually detects a scroll up key binding when the viewport hasn't changed.

The corresponding check will never come into play in the "down" direction unless the user specifies `--limit=1`, at which point they clearly don't want more logs anyway so we shan't provide them.

* Actually allow pagination requests to fetch 1000 logs at a time
    @blue-keleher
    blue-keleher authored Dec 8, 2025
    Configuration menu
    Copy the full SHA
    3c74b02 View commit details
    Browse the repository at this point in the history
Loading