docs: convert list/pag/progb/progs/rad/rip/elev to signals#33497
Merged
crisbeto merged 1 commit intoJul 7, 2026
Merged
Conversation
crisbeto
approved these changes
Jul 7, 2026
Member
crisbeto
pushed a commit
that referenced
this pull request
Jul 7, 2026
(cherry picked from commit 8205e24)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Converts the following components to use signals
Part of an effort to address this issue about compatibility with new defaults: #33443
Ripple and Elevation are considered "Core" items, but have no "Examples" section in the "Core" page. However, Ripples are in the docs Components sidenav and the "Examples" tab houses the example that was updated.
And I also converted a (core) elevation example. Unlike Ripple which was a "Components" sidenav item whose example is nested under the
/corefolder of the component examples, I could not find usage of Elevation in practice in the docs. So I was not able to smoketest it, but it should be legit as I double checked it when reviewing my code first.PR scope
I thought that 7 components worth of changes was a good chunk. There is more chunks to come for other components.
This time around I only made this one branch, since the last PR as one chunk worked well: #33492. Thank you.
Extras
For personal reference, here is my checklist of doc examples worked through: https://gist.github.com/msmallest/f77adb004b9e88c49b3a248bab90a26a?permalink_comment_id=6237101#gistcomment-6237101