material-components / material-components/material-components-android
[FlowLayout] Move FlowLayout outside of internal
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.4k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
I want to use FlowLayout but it is marked as internal to the library so I cannot use or extend it
**Describe the solution you'd like**
I would like for `FlowLayout` to be available to use publicly.
**Describe alternatives you've considered**
Currently `ChipGroup` extends this but it feels out of place to use `ChipGroup` without having `Chips` as the children
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 FlowLayout and ChipGroup entry points in the Android library and checking how FlowLayout is marked internal. Review the related tests, if present, and confirm that FlowLayout can be used and extended publicly without requiring ChipGroup; the issue is done when that public usage is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100