dotnet / dotnet/project-system
Create separate browse object rules for dependency node items
Open
Feature-Dependency-Node
Feature-Rules/Properties
Performance-Scenario-Solution-Open
Priority:2
Tenet-Performance
Triage-Approved
- Dominant language
- C#
- Stars
- 1k
- Forks
- 415
- PR merge metrics
- No merged PRs in 30d
Description
Currently the DTB targets called by the dependencies node have rules that include many properties as those rules are used both by the logic of the dependencies node itself, and also as the browse object that backs the properties panel.
We should break this in two, creating separate rules for the browse objects.
Contributor guide
Assessment
This issue has not been assessed yet.