Skip to content

Completion Support #1007

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

Merged

Conversation

TylerLeonhardt
Copy link
Member

No description provided.

case CompletionResultType.Type:
return CompletionType.Type;

case CompletionResultType.Keyword:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should map DynamicKeyword to CompletionType.Keyword?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think those are falling into CompletionType.Unknown?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suppose so but to be honest this is a feature (dynamic keywords) where I have little experience. Just seemed like low hanging fruit. :-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if that could be causing some issues with loading of completions of dynamic parameters... probably not. I'll still add it. Thanks!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably not causing dynamic parameter issues. Unless you're using DSC, it's unlikely you'd see any issue here

@rkeithhill
Copy link
Contributor

Will this only support v5 AST and later? If so, can we finally add class/enum icons for completion intellisense? Also, will want to add that for document symbols. Perhaps in a separate PR though.

@TylerLeonhardt
Copy link
Member Author

Will this only support v5 AST and later?

Yep!

If so, can we finally add class/enum icons for completion intellisense?

This should work today because the API hasn't changed... I think.

Where we're lacking on class/enum support is symbols used in references. I could be wrong here.

@TylerLeonhardt
Copy link
Member Author

rebased on the new C# E2E tests and things look good!

@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@PowerShell PowerShell deleted a comment Aug 20, 2019
@TylerLeonhardt TylerLeonhardt merged commit 602c1fd into PowerShell:omnisharp-lsp Aug 21, 2019
@TylerLeonhardt TylerLeonhardt deleted the omni-completion branch August 21, 2019 19:48
TylerLeonhardt added a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Oct 3, 2019
* completion support

* misc codacy fixes

* use BUILD_ARTIFACTSTAGINGDIRECTORY so logs can be uploaded

* publish artifacts even if build fails

* handle log messages

* give PSES a chance to run what it needs to run

* switch to using xUnit output helper

* treat DynamicKeywords as Keyword
TylerLeonhardt added a commit that referenced this pull request Oct 3, 2019
* Add starting point

* x

* More work

* Make integration tests pass for omnisharp

* Changes

* add dummy workspace symbols handler

* use LoggerFactory

* A working WorkspaceSymbolsHandler

* working text document syncer

* needed document selector and getVersion handler to work with vscode

* Added Diagnostics

* didChangeConfiguration message and general settings support

* Add diagnostics (#18)

* initial folding support

* added test for folding

* Add setting support (#19)

* Added Diagnostics

* didChangeConfiguration message and general settings support

* Apply suggestions from code review

Co-Authored-By: Robert Holt <[email protected]>

* Folding support (#20)

* Added Diagnostics

* didChangeConfiguration message and general settings support

* initial folding support

* log level trace

* folding works with latest omnisharp version

* comment typo

* added test for folding

* formatting support

* remove merge conflict

* add formatting tests

* DocumentSymbols and References support (#997)

* working formatting

* add tests

* delete commented out code

* [Omnisharp-LSP] textDocument/documentHighlight support (#999)

* Add handler scaffold

* More stuff

* Make handler work

* Add copyright

* Add tests, fix bugs

* Fix small issues

* codelens support (#1001)

* codelens support

* address rob's feedback

* powerShell/getPSHostProcesses and powerShell/getRunspace (#1002)

* Test only pester for now (#1003)

* Implement textDocument/codeAction (#1004)

* Add initial handler

* Add working codeAction implementation

* Crash

* Make tests work

* Fix issues

* Make tests work in WinPS

* Add powershellcontext (#1005)

* Add powershellcontext

* using file sink now instead

* all the newlines

* support $psEditor (#1006)

* support $psEditor

* deleted commented out code

* fix initial build failures due to lack of certain assemblies

* use different RootPath

* wait an extra 5 seconds just in case

* refactor initialize script

* Re-add Stdio option and replace Pester tests with xunit tests. (#1008)

* Completion Support (#1007)

* completion support

* misc codacy fixes

* use BUILD_ARTIFACTSTAGINGDIRECTORY so logs can be uploaded

* publish artifacts even if build fails

* handle log messages

* give PSES a chance to run what it needs to run

* switch to using xUnit output helper

* treat DynamicKeywords as Keyword

* completionresolve support (#1009)

* handle log messages

* switch to using xUnit output helper

* Add completionItem/resolve request

* feedback

* update build to run update-help for signature help test

* removing scope hoping it works in CI

* setting to EA silentlycontinue

* change to language=powershell

* hover support (#1010)

* handle log messages

* switch to using xUnit output helper

* add hover handler

* move to language=powershell

* refactoring for feedback

* codacy

* Omni signaturehelp (#1011)

* handle log messages

* switch to using xUnit output helper

* Support SignatureHelp

* concurrentdict

* Add definition handler (#1013)

* add definition handler

* codacy

* sneak in powerShell/executionStatusChanged

* codacy

* Add Plaster messages (#1014)

* Comment Help and Evaluate (#1015)

* Support for Comment Help generator

* add evaluate handler

* Last LSP messages (#1016)

* support CommandExporer commands and powerShell/runspaceChanged

* expand alias

* refactor server setup (#1018)

* rename namespaces (#1019)

* The entire Debug Adapter moved over... (#1043)

* initial non-working dap

* working launch but not attach

* working attach handler

* update namespaces

* Disconnect support and handling of JsonRpcServer teardown

* Add foundation for debug tests - stdio and fixures

* all handlers

* remote file manager working

* rest of debug adapter

* use actual release

* Apply suggestions from code review

Co-Authored-By: Robert Holt <[email protected]>

* Delete projects we wont be keeping around and get pses.vscode working again (#1046)

* delete other folders and tweak build script for BuildInfo

* working PowerShellEditorServices.VSCode now a binary module!

* some typo

* Apply suggestions from code review

Co-Authored-By: Patrick Meinecke <[email protected]>

* address additional comments

* don't checkin maml

* add error handling

* deleted buildinfo and address rob's comments

* Remove engine from files and namespaces (#1048)

* apply apt state for PS7 (#1051)

* delete buildinfo

* implement powerShell/startDebugger (#1049)

* implement powerShell/startDebugger

* add line

Co-Authored-By: Patrick Meinecke <[email protected]>

* Enable alias corrections (#1053)

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

Successfully merging this pull request may close these issues.

3 participants