TeamAmaze / TeamAmaze/AmazeFileManager
Move layouts to ConstraintLayout
Open
Nobody has claimed this yet.
Issue-Feature
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Use ConstraintLayout, it will help with some really deeply nested layouts (that affect performance) and they are easily editable from the Layout Editor's visual tools.
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 inventorying the Android layout resources and identifying the deeply nested layouts referenced in the issue. Review the linked ConstraintLayout and layout-performance guidance before planning the migration. Done means the relevant nested layouts use ConstraintLayout and the app's layout behavior and performance remain intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100