feat_favorites_homepage_section

[Mbeaulne]

Description

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

Additional Comments

[github-actions]

🎩 To tophat this PR:

You can add the following URL parameter to your browser to tophat this PR:

`?tophat_location=03-23-feat_favorites_homepage_section/c697d88`

---

[Mbeaulne]

• remove old home page #2056
• Default dashboard flag #2055
• Add components section #2025
• Add dashboard home view with favorites, recently viewed, and my runs sections #2011
• moves app footer #2010
• add new section to the side bar #2004
• Updates runs and pipelines designs #2003
• Adds runs and filters #2002
• update favourite and recent cards #2001
• Updates revently viewed #2000
• Adds recently viewed #1999
• Update design for favourites #1998
• add favourites to new dashboard #1997
• feat dashboard layout #1996
• Feat recently viewed #1986
• feat_favorites_filter #1985
• feat_favorites_homepage_section #1983 👈 (View in Graphite)
• feat_favorites_toggle_ui #1982
• feat favorites infrastructure #1980
• Dashboard and beta #1932
• Add Claude AI skills for project conventions and development standards #1931
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Mbeaulne]

Reviewer note: FavoritesSection.tsx (the chip-based layout introduced here) is deleted in #1996 as part of a design pivot away from chips toward cards. It is briefly re-added verbatim in #1997 and then deleted again in #1998.

You can treat this PR as exploratory UI iteration — the final favorites design lives in DashboardFavoritesView.tsx (#1998+). No need to give deep feedback on the chip layout.

[camielvs]

You can treat this PR as exploratory UI iteration — the final favorites design lives in DashboardFavoritesView.tsx (#1998+). No need to give deep feedback on the chip layout.

Hah I should have read this first.

Curious why not just remove this PR from the stack?

[camielvs]

Based on your comment my understanding is that I should just ignore this PR and let it be merged as part of the stack.

The comments may still be useful though, for other areas

[Mbeaulne]

Merge activity

• Apr 10, 8:38 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Apr 10, 8:50 PM UTC: Graphite rebased this pull request as part of a merge.
• Apr 10, 8:52 PM UTC: @Mbeaulne merged this pull request with Graphite.