Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: NaviBar Symbol Scope Filter and Other Improvements #343

Open
fitdev opened this issue Jan 5, 2025 · 1 comment
Open

Suggestion: NaviBar Symbol Scope Filter and Other Improvements #343

fitdev opened this issue Jan 5, 2025 · 1 comment
Labels

Comments

@fitdev
Copy link

fitdev commented Jan 5, 2025

Symbol Scope Filter

Currently NaviBar works that it shows all namespaces and types within the whole solution as well as all the referenced assemblies (framework, nugets).

This is nice, but it is often slow (and sometimes not consistent - depending on which project's document you are accessing NaviBar from - it may show different types and namespaces - i.e. it will not show all types and namespaces from your solution).

It would be nice to perhaps place on the right-most side a dropdown selection of the current filter mode for the NaviBar with the following choices:

  1. Everything - the way it current works - entire solution + all references - whether framework or nugets
  2. Current Project/Assembly only
  3. Current Project + all Dependency Projects (i.e. all user code that includes the current project as well as all the projects the current projects depends on)
  4. Entire solution - all user code (without any of the framework packages or nugets)
  5. The inverse of 4: external, non-user-code only - all framework and nuget packages

Obviously all the choices here would exclude the current document since it would always be visible (as well as possibly its partial files and base types).

Regions Support in Search Declaration

It is common to nest multiple small types within #regions for better organization. It would be nice if NaviBar's Search Declaration dropdown would reflect that (currently NaviBar supports regions only within types).

Screenshot_20250105_135508

#region R1
interface I1 { }
interface I2 { }
#endregion

#region R2
interface I3 { }
interface I4 { }
#endregion

Should produce the menu:

Region R1
  Interface I1
  Interface I2
Region R2
  Interface I3
  Interface I4
@fitdev
Copy link
Author

fitdev commented Jan 13, 2025

It would also be nice to have similar filters (or at the very least in as far as user-code (solution-item) vs framework code / reference distinctions) in the find symbol result list - the pinnable window that appears after searching for some symbols (like all classes that inherit from...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants