Improving retaining path identifier in Diff view
Open
memory > diff
P3
screen: memory
ux
- Dominant language
- Dart
- Stars
- 1.7k
- Forks
- 404
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 18
Description
Retaining paths are currently identified by the last few nodes as shown in the screenshot below. The identifiers often include classes internal to Dart and Flutter, which the app developer is likely to be unfamiliar with. Thus, it's unclear the information in such identifiers actually providing any value to the majority of users.
It might not hurt to identify different retaining paths simply by number such as Path 1, Path 2, Path 3, etc. The detailed path information is available on the right hand side of the table once the user selects one of them. Thoughts?
Contributor guide
Assessment
This issue has not been assessed yet.