Account for function and variable scope in language service features #16

Activity

1. kaylaerdmann

   added

   Issue-BugA bug to squash.A bug to squash.

   on Aug 12, 2015
2. David Wilson (daviwil)

   modified the milestone: 0.1.0 on Aug 13, 2015
3. daviwil commented on Nov 9, 2015

   

   David Wilson (daviwil)

   on Nov 9, 2015

   Contributor

   More actions

   This requires similar logic to #28 so potentially both could be developed at the same time.
4. David Wilson (daviwil)

   added

   Up for GrabsWill shepherd PRs.Will shepherd PRs.

   on Nov 9, 2015
5. David Wilson (daviwil)

   modified the milestones: 0.2.0, 0.1.0, 0.3.0 on Nov 16, 2015
6. David Wilson (daviwil)

   modified the milestones: 0.3.0, BacklogThis milestone has been deleted on Dec 31, 2015
7. David Wilson (daviwil)

   changed the title [-]Use correct scope on variables and parameters for intellisense features[/-] [+]Consider variable scope for language intelligence features[/+] on May 18, 2016
8. David Wilson (daviwil)

   changed the title [-]Consider variable scope for language intelligence features[/-] [+]Account for function and variable scope in language intelligence features[/+] on May 18, 2016
9. David Wilson (daviwil)

   changed the title [-]Account for function and variable scope in language intelligence features[/-] [+]Account for function and variable scope in language service features[/+] on May 18, 2016
10. TylerLeonhardt

    added

    Area-Code Navigation

    Area-IntelliSense

    and removed

    Up for GrabsWill shepherd PRs.Will shepherd PRs.

    on Jan 17, 2018
11. TylerLeonhardt

    added a commit that references this issue on Jul 16, 2019

    Merge pull request PowerShell#16 from TylerLeonhardt/working-workspac…

    ...

    b022751
12. Andy Jordan (andyleejordan)

    removed this from the BacklogThis milestone has been deleted milestone on Aug 17, 2021
13. fflaten commented on Jan 15, 2023

    

    Frode Flaten (fflaten)

    on Jan 15, 2023

    Last edited by fflaten

    Contributor

    More actions

    Adding an example of this:

    function myDemo ($o) {
        $o = "second"
    }
    
    $o = "first"
    $o # Go to definition here will go to first match -> reassignment on line 2

    Update: Preview extension v2023.2.0 includes change from #1984 which now shows all definitions. Good enough? Matching scope is hard, so not sure if/when that will be fixed.
14. andyleejordan commented on Jun 15, 2026

    

    Andy Jordan (andyleejordan)

    on Jun 15, 2026

    Last edited by andyleejordan

    Member

    More actions

    Resolved by #1990 (v3.8.1) — language features now strip scope qualifiers (VisitorUtils.GetUnqualifiedFunctionName), so scoped function/variable names resolve correctly. Closing as completed.

    ---

    Drafted by GitHub Copilot (Claude Opus 4.8) at Andy Jordan (@andyleejordan)'s request.
15. Andy Jordan (andyleejordan)

    closed this as completedon Jun 15, 2026