Skip to content

Add source to component search v1 and v2#2469

Merged
Mbeaulne merged 1 commit into
masterfrom
06-29-add_source_to_component_search_v1_and_v2
Jun 29, 2026
Merged

Add source to component search v1 and v2#2469
Mbeaulne merged 1 commit into
masterfrom
06-29-add_source_to_component_search_v1_and_v2

Conversation

@Mbeaulne

@Mbeaulne Mbeaulne commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

Description

Component items in the sidebar now display a digest identifier as a fallback when no published_by value is present (e.g. Digest sha256:abc123). Previously, only components with a published_by value showed secondary metadata beneath the display name.

On the Dashboard component cards, the publisher label has been updated from by <publisher> to Published by <publisher> for consistency with the sidebar, and the label is now visible in both the expanded and compact (selected-result) states, with appropriate indentation when the detail panel is open.

source metadata is now forwarded to ComponentMarkup in ComponentSearchResults so that result items can reflect which source (e.g. "Published") they came from.

Related Issue and Pull requests

Type of Change

  • Bug fix
  • New feature
  • Improvement
  • Cleanup/Refactor
  • Breaking change
  • Documentation update

Checklist

  • I have tested this does not break current pipelines / runs functionality
  • I have tested the changes on staging

Screenshots (if applicable)

Test Instructions

  1. Open the component sidebar and search for a component that has no published_by value but does have a digest. Confirm the secondary label reads Digest <digest>.
  2. Search for a component that has a published_by value. Confirm the secondary label reads Published by <publisher>.
  3. On the Dashboard components view, search for a published component and confirm Published by <publisher> appears both in the search result card and when the component is selected (compact row).

Additional Comments

New unit tests cover the digest fallback display in SearchResults, publisher visibility in DashboardComponentsV2View, and source metadata forwarding in ComponentSearchResults.

@github-actions

github-actions Bot commented Jun 29, 2026

Copy link
Copy Markdown

🎩 Preview

A preview build has been created at: 06-29-add_source_to_component_search_v1_and_v2/567d072

@Mbeaulne Mbeaulne force-pushed the 06-29-add_source_to_component_search_v1_and_v2 branch from a69b20d to 9e6c40c Compare June 29, 2026 17:06
@Mbeaulne Mbeaulne marked this pull request as ready for review June 29, 2026 17:17
@Mbeaulne Mbeaulne requested a review from a team as a code owner June 29, 2026 17:17
@Mbeaulne Mbeaulne force-pushed the 06-29-add_editor_component_search_loading_skeleton_matt branch from c102a63 to bb5303a Compare June 29, 2026 17:20
@Mbeaulne Mbeaulne force-pushed the 06-29-add_source_to_component_search_v1_and_v2 branch from 9e6c40c to 6d06235 Compare June 29, 2026 17:20
@Mbeaulne Mbeaulne changed the base branch from 06-29-add_editor_component_search_loading_skeleton_matt to graphite-base/2469 June 29, 2026 17:57
@Mbeaulne Mbeaulne force-pushed the graphite-base/2469 branch from bb5303a to 713cd2a Compare June 29, 2026 18:01
@Mbeaulne Mbeaulne force-pushed the 06-29-add_source_to_component_search_v1_and_v2 branch from 6d06235 to 81d1273 Compare June 29, 2026 18:01
@graphite-app graphite-app Bot changed the base branch from graphite-base/2469 to master June 29, 2026 18:02
@Mbeaulne Mbeaulne force-pushed the 06-29-add_source_to_component_search_v1_and_v2 branch from 81d1273 to 567d072 Compare June 29, 2026 18:02

Mbeaulne commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator Author

Merge activity

  • Jun 29, 6:06 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jun 29, 6:06 PM UTC: @Mbeaulne merged this pull request with Graphite.

@Mbeaulne Mbeaulne merged commit 741af61 into master Jun 29, 2026
17 checks passed
@Mbeaulne Mbeaulne deleted the 06-29-add_source_to_component_search_v1_and_v2 branch June 29, 2026 18:06
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.

2 participants