PowerShellEditorServices
PowerShellEditorServices copied to clipboard
PowerShell
Add language feature support for classes
The following features do not work when inside a class:
- Parameter hints
- Get Definition
- Get References
- Change Occurrences
- Symbol search
When outside of a class all features work normally.
Probably can't make this in for 0.1.0, will get it out soon after for 0.2.0.
Hey Brian, not at the moment, but we'll definitely be adding it within the next few releases. Which features have you been missing the most for classes so far?
Can you give an example of what you mean by intelligent auto-completion? Parameter hints for class methods are definitely coming!
Right now, the only completion feature VS Code has when working with classes is if it see I am typing a word that already exist, it will suggest it. What I mean is: only show me the methods and constructors for the respective class type. Furthermore, it would be nice if it understood the value-types I am currently typing and show the respective signature(s) as hints or show warnings when it the object doesn't have signature the for values being pass (assuming the value was explicitly typed).
@kapilmb, any chance you might be able to help with this one for 0.8.0 release (early October)?
@daviwil Sorry for getting back so late about this. Sure, you can assign this to me if you haven't started work on it already.
Any updates on this? Symbol search on class definitions/methods would be very nice.
This issue is closed for a long time, but it doesn't really work. No symbols search, no go to definition, no itellisense for classes and methods on dot sourced files... Any updates? Can provide screenshots of things that are not working if you need examples.
Hi. Any news about symbol search in classes? It has been "must have" feature since Powershell 5.0.
IIRC PSES uses the v3 AST to cover all supported versions of PowerShell (v3-6). We've been talking about dropping support for v3/4 in the editor in the next major version of the extension. This would allow us to move to the v5 AST which recognizes class and enum. I think that would be relatively easy. If we need to continue to support back to v3 then we need a runtime swappable provider for both v3 and v5 ASTs. That's doable but would take more time.
Hello, I need this functionality too. Some years ago, I created an addon for PowerShell ISE to manage group of PS scripts in a similar way folders are used with VSCode (it is in GitHub too if some one need it). I added to it the "Get definition" and "Get references" functionalities covering classes too.
Now I 'm working with VSCode to manage different language files (including PS) under the same folder and the lack of those two functionalities is so annoying that I had to implement it.
Probably it is not the best way to implement it but it works. I don't know if it is worth proposing a pull request for this change since this functionality will already be available in a next major version.
In any case, it is located in this fork if you want to review it.
@livianaf if you would like to send a PR that would be awesome :) this is highly requested and what better time to send a PR than Hacktoberfest!
Uf! I got too many errors I don't know how to manage :(
I'm sorry, this is my first PR. How can I get the detail of the errors generated by the PR checks?
Fixed by https://github.com/PowerShell/PowerShellEditorServices/pull/1984
