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

Find all references on an imported member shows the definition in the reference list #792

Closed
andygraham opened this issue Aug 26, 2015 · 0 comments · Fixed by #1226
Closed
Assignees
Labels

Comments

@andygraham
Copy link

VS Desktop Express 2013, IronPython 2.7.5, PTVS Dev 2015-08-21 VS 2013

This is a minor, slightly untidy cosmetic discrepancy, possibly not worthy of your attention :) and maybe even by design, but if so I don't see why :(

Right-click -> Find All References on an imported item, from a pure Python code module or a .NET assembly, seems to tag the definition line onto the end of the References list in the Find Symbol Results window as well as showing it in the Definitions list. It doesn't do this for anything defined in the current module

@DinoV DinoV self-assigned this Apr 12, 2016
DinoV pushed a commit to DinoV/PTVS that referenced this issue Apr 15, 2016
DinoV pushed a commit to DinoV/PTVS that referenced this issue Apr 15, 2016
Add a Extract Method suggested action and include a preview of the new
change

Add a PreviewChangesService for creating a preview text view based upon a
set of changes

Fix microsoft#186
 Special case checking for REPL buffers that start with a $ and don't
 provide quick info. Unfortunately we have to do that because the REPL window
 input kind doesn't change until we have a complete input

 Fix microsoft#792
 Clean up our BufferParser/AnalysisEntry/TextView tracking so that we can
 support this.  We no longer attach any properties to text buffers at all.
 Instead we always resolve from textview and/or filename into a
 ProjectAnalyzer and then get the buffer from there.

 We now flow TextView's where they're available into our analyzer.
 There's only really 3 spots where we don't have that full context: Outlining
 regions and proximity info via the old IVsLanguageInfo interfaces.

 Add support for CommonPackage.GetActiveTextView so that we can find the
 correct active text view for diff windows. This is used all over the
 place to find the text view when we're doing various editing commands like
 extract method, find all refs, goto def, etc...

 Update Extensions to add various helpers which deal with the caret
 within a projection buffer.
@DinoV DinoV mentioned this issue Apr 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants