material-components / material-components/material-components-android
[List] Add feature for saving List component settings to persistent storage
@imhappi y travaille déjà.
Depuis le 21/1/2026.
- Langage dominant
- Java
- Étoiles
- 17.4k
- Forks
- 3.2k
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
**Description of current situation**
If I understand correctly, the [M3 Expressive Lists](https://github.com/material-components/material-components-android/blob/master/docs/components/List.md) are the new way for building a [Preference Screen](https://developer.android.com/develop/ui/views/components/settings/organize-your-settings) as the `PreferenceScreen` is obviously not redesigned anymore for M3 (Expressive).
Currently, the Catalog app contains some M3 Expressive examples with `Lists` (ListItemCardView), including components such as RadioButtons (`MaterialButton`), CheckBoxes (`MaterialCheckBox`), etc.
**Describe the solution you'd like**
It would be great if you can add a small feature / enhancement e.g. to the ListItemCardView example that shows how to save the settings, e.g. from RadioButtons (`MaterialButton`), CheckBoxes (`MaterialCheckBox`), etc. to the persistent storage. When closing / re-opening the app, the settings should be reloaded from the persistent storage.
See https://github.com/material-components/material-components-android/issues/4997 & https://github.com/material-components/material-components-android/issues/4940
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Évaluation
Cette issue n'a pas encore été évaluée.