Review FlexLayoutManager measurement for possible performance improvements
Open
area-layout
layout-flex
perf/general
s/triaged
t/bug
- Dominant language
- C#
- Stars
- 23.3k
- Forks
- 2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 290
Description
FlexLayoutManager is currently looping over the child views to measure the full size of the FlexLayout. It's likely we can work out a way to simply retrieve the root Frame of the FlexLayout and use that measurement instead, which should perform a bit better.
Contributor guide
Research direction
Start by locating FlexLayoutManager and tracing how it loops over child views to measure the full FlexLayout. Compare that path with the root Frame measurement described in the issue, and establish whether the alternative is correct and measurably faster. Done means a validated performance improvement with appropriate evidence, but no test or file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- frontend, mobile-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100