feat(MatRipple): The style of the ripple component is still in the M2 state, whether to consider upgrading to M3?
Open
Nobody has claimed this yet.
area: material/core
feature
P3
- Dominant language
- TypeScript
- Stars
- 25k
- Forks
- 6.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 91
Description
Feature Description
Hi all, is there any plan to upgrade the styling of MatRipple components to M3?
Use Case
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MatRipple implementation and comparing its current M2 styling with the repository’s M3 conventions. Determine the styling changes and validation needed before implementation; done means MatRipple follows the agreed M3 treatment and its relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100