Skip to content

[FEATURE] Add optional projectName prop to ViewExplore#104

Open
rickardsjp wants to merge 1 commit intoperses:mainfrom
rickardsjp:explore-project-name
Open

[FEATURE] Add optional projectName prop to ViewExplore#104
rickardsjp wants to merge 1 commit intoperses:mainfrom
rickardsjp:explore-project-name

Conversation

@rickardsjp
Copy link
Copy Markdown

Description

DatasourceStoreProvider already accepts a projectName prop (every dashboard uses it), but ViewExplore wasn't forwarding it, so explore was limited to global datasources. This threads the prop through as an optional addition to ViewExploreProps.

Existing consumers are unaffected since the prop defaults to undefined.

Relates to perses/perses#3005

Screenshots

n/a: No visual change. The prop is consumed by the Perses app layer which provides the UI.

Checklist

  • Pull request has a descriptive title and context useful to a reviewer.
  • Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
    following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
  • All commits have DCO signoffs.

UI Changes

n/a: No direct UI changes in this PR. UI is provided by the consuming app.

@rickardsjp rickardsjp requested a review from a team as a code owner April 13, 2026 21:13
Thread the already-existing DatasourceStoreProvider projectName
prop through ViewExplore so consumers can scope the explore view
to a specific project's datasources.

Signed-off-by: Jeremy Rickards <jeremy.rickards@sap.com>
@rickardsjp rickardsjp force-pushed the explore-project-name branch from c265e16 to 017b729 Compare April 13, 2026 21:14
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.

1 participant