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
Similar to how it is possible with Codist to differentiate between user and non-user code in the editor, it would be nice if it were possible to also differentiate user from non-user code in the Intellisense dropdowns.
Several approaches might be possible (or a combination of them):
Make user or non-user code bold (perhaps controlled by an option)
Add a suffix with assembly name or namespace in a different style (perhaps similar to how unimported namespaces members are displayed)
Modify the tooltip that appears as the user selects different members in the dropdown list, so it shows namespace and/or assembly information (and perhaps uses syntax styles defined for Codist as well).
Add a dedicated filter button (similar to field, property, method, etc. filters) that can work in addition to existing member-type filters.
The first 2 approaches need special handling of methods, since they have overloads and therefore can both be of user and of non-user code. So, perhaps, if there is at least one overload which is a user-code, then the list item should be stylized as such. Alternatively (and perhaps even better idea) is to have a 3rd style for list items that have both overloads from user and non-user code.
The text was updated successfully, but these errors were encountered:
Thanks for taking time posting a duplicated request. I remember your request quite well. And I want that too!
Recently Visual Studio guys have posted a questionnaire to gather suggestions to change the extension development experience. I recommended Codist to them. Hope that they can take a look at this project and your suggestions as well.
Similar to how it is possible with Codist to differentiate between user and non-user code in the editor, it would be nice if it were possible to also differentiate user from non-user code in the Intellisense dropdowns.
Several approaches might be possible (or a combination of them):
The first 2 approaches need special handling of methods, since they have overloads and therefore can both be of user and of non-user code. So, perhaps, if there is at least one overload which is a user-code, then the list item should be stylized as such. Alternatively (and perhaps even better idea) is to have a 3rd style for list items that have both overloads from user and non-user code.
The text was updated successfully, but these errors were encountered: