The ability to add a field to the inspector that shows a dropdown of Yarn Nodes in a particular project is nice but there are clear use cases for more nuanced modes of interaction which filter the nodes shown instead of always having the full list. This is most relevant for large projects, projects which make heavy use of small nodes, or projects where many nodes are not entry points.
Ideas:
- Filter by search (either text match or regex match, and even inverse/non-match)
- Filter by node tag(s)
- Filter by some static setup of parameters which are set at inspector init time (e.g. omit nodes with names that start with "Debug")
- Other options which may be overkill like "filter by character name that speaks in this node"
At least the first two have been requested multiple times, and often even added by people themselves. So the implementation should be simple; many examples exist in our Discord channels already.
The ability to add a field to the inspector that shows a dropdown of Yarn Nodes in a particular project is nice but there are clear use cases for more nuanced modes of interaction which filter the nodes shown instead of always having the full list. This is most relevant for large projects, projects which make heavy use of small nodes, or projects where many nodes are not entry points.
Ideas:
At least the first two have been requested multiple times, and often even added by people themselves. So the implementation should be simple; many examples exist in our Discord channels already.