Skip to content

fix(frontend): add refresh button to artifact detail page#9384

Open
DharmaBytesX wants to merge 1 commit into
opsmill:stablefrom
DharmaBytesX:fix-9335-artifact-page-refresh-button
Open

fix(frontend): add refresh button to artifact detail page#9384
DharmaBytesX wants to merge 1 commit into
opsmill:stablefrom
DharmaBytesX:fix-9335-artifact-page-refresh-button

Conversation

@DharmaBytesX
Copy link
Copy Markdown
Contributor

@DharmaBytesX DharmaBytesX commented May 29, 2026

Why

When viewing an artifact on its detail page and triggering the regenerate action, there was no control to reload the artifact view once generation finished. The content stayed stale until the whole browser tab was refreshed.

Closes #9335

What changed

The shared refresh button now appears in the artifact header, right next to the regenerate action. Clicking it refetches the artifact object and its rendered content directly on the page, so the updated output becomes visible without reloading the entire browser tab.

This reuses the existing refresh button component that object detail pages already rely on, so the appearance, the loading state, and the last refresh tooltip stay consistent across the application. No backend changes and no API changes were needed.

How to test

  1. Start a local instance with demo data that includes artifacts.
  2. Open an artifact detail page at /objects/CoreArtifact/{id}.
  3. Confirm a refresh button now sits to the left of the regenerate action.
  4. Click regenerate, wait for the activity panel to report the artifact as ready, then click refresh and confirm the new content loads in place.

Automated checks:

cd frontend/app
pnpm biome check src/entities/artifacts/ui/artifact-header.tsx
pnpm test

The frontend unit suite passes (657 tests across 89 files) and Biome reports no issues on the changed file.

Impact

Backward compatibility: no breaking changes, the behavior is additive only.

Performance: negligible, the refresh action runs the same query the page already performs.

Config or environment changes: none.

Checklist

  1. Changelog entry added.
  2. Change verified in a running instance.
  3. No new automated tests, since the change reuses a component that is already covered by existing tests.

Summary by cubic

Add a refresh button to the artifact detail page to show regenerated output without reloading the tab, addressing #9335. The shared RefreshButton sits next to Re-generate and refetches the artifact and its rendered content in place.

Written for commit c338a36. Summary will update on new commits.

Review in cubic

The artifact detail page offered no way to reload the artifact view
after regenerating it, so the only way to see updated content was a
full browser refresh.

This adds the shared refresh button to the artifact header, next to
the regenerate action. Clicking it refetches the artifact object and
its rendered content in place, matching the refresh behavior already
used on object detail pages.

Closes opsmill#9335
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(frontend): no refresh button on artifact page after re-generating

1 participant