Skip to content

PowerShell Local Configuration Manager Autocomplete adds extra characters #45

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

Closed
duffney opened this issue Dec 8, 2015 · 2 comments
Closed
Labels
Issue-Bug A bug to squash.

Comments

@duffney
Copy link

duffney commented Dec 8, 2015

When writing LCM configuration with Code I found that it adds an extra character at the beginning of the code when using the intelisense. Example seen below, if you use intelisense to autocomplete the settings of the LCM it leaves the first character you typed to search for completion.

[DscLocalConfigurationManager()]
Configuration LCMPull {
    Node Localhost {
        Settings {
            aActionAfterReboot = 'ContinueConfiguration'


        }
    }
}
@daviwil daviwil added the Issue-Bug A bug to squash. label Dec 8, 2015
@daviwil
Copy link
Contributor

daviwil commented Dec 8, 2015

Thanks Josh!

@daviwil
Copy link
Contributor

daviwil commented Dec 11, 2015

Now fixed in PowerShellEditorServices, look for this is the next release!

@daviwil daviwil closed this as completed Dec 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

2 participants