Skip to content

Add CompletionItemKind.Folder. #364

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
merged 1 commit into from
Feb 3, 2017

Conversation

rkeithhill
Copy link
Contributor

They finally added this in 1.9.0. Noticed as I was reading through the release notes.

They finally added this in 1.9.0. Noticed as I was reading through the release notes.
@rkeithhill
Copy link
Contributor Author

rkeithhill commented Feb 3, 2017

I'm not sure how VSCode < 1.9 will handle an enum value it doesn't understand. If it ignores it then we're good. If not, then I guess we'd have to set the min version to 1.9. Here is what it looks like:

image

Hmm, interesting that the c from the c: seems to be picked up for fuzzy matching. Weird.

@daviwil
Copy link
Contributor

daviwil commented Feb 3, 2017

Damn, they finally added it! I would guess that it won't crash at the very least. If it does we'll just tell people to upgrade.

@daviwil daviwil merged commit 7a10453 into develop Feb 3, 2017
@daviwil daviwil deleted the rkeithhill/add-completionitemkind-folder branch February 3, 2017 14:24
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Feb 26, 2019
* Add support for debug configurationSnippets.

Rename debug target from "PowerShell" to "PowerShell Launch (current file)" this makes room for an eventual "PowerShell Attach" debug target.

Fix PowerShell#364.

* Replace tabs with spaces in copy/pasted config.
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