You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub snippet provider generates 4 (or 5) snippets for every repository. It could generate even more snippets (pulls, settings, discussions, actions, code search, etc). But that would flood the snippet list in current implementation.
1. Scoping like app filter
We could create kind of scoping. Idea is that if user presses TAB on selected snippet, it will scope the search to include only sub snippets for the selected one. Some snippet would act as a folders (not applyable) or combination (applyable + containing sub snippets).
The scoping UI coould look like app filter (#4) where pressing backspace on empty search box will drop the scoping filter.
Cons
Currently the user can write "Snipp Mana iss" to find a snippet for list of issues on this repo. After the proposed changes, user would need to the 2 steps: Write "Snipp Mana", press TAB, write "iss".
To mitigate the extra step, we could automatically add sub snippets if filtered list of snippets contains 1 (or X) items.
2. Tree view
Other approach would be to use tree view for displaying snippets. Search will filter only root snippets. When the user opens a tree item, searching will start to look in there.
Cons
As we show only 5 items, the window's height will either grow or we will show only few items.
Missing the scoping might be harder for orientation.
The text was updated successfully, but these errors were encountered:
GitHub snippet provider generates 4 (or 5) snippets for every repository. It could generate even more snippets (pulls, settings, discussions, actions, code search, etc). But that would flood the snippet list in current implementation.
1. Scoping like app filter
We could create kind of scoping. Idea is that if user presses
TAB
on selected snippet, it will scope the search to include only sub snippets for the selected one. Some snippet would act as a folders (not applyable) or combination (applyable + containing sub snippets).The scoping UI coould look like app filter (#4) where pressing backspace on empty search box will drop the scoping filter.
Cons
TAB
, write "iss".2. Tree view
Other approach would be to use tree view for displaying snippets. Search will filter only root snippets. When the user opens a tree item, searching will start to look in there.
Cons
The text was updated successfully, but these errors were encountered: