Skip to content

Fix snippet placeholder formatting #795

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
May 30, 2017
Merged

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented May 30, 2017

This change fixes some ambiguity in our snippet placeholders to confirm
with stricter parsing rules in VS Code 1.12.0. Generally this requires
prefixing an index (${1:Placeholder Text}) anywhere that a placeholder
is used so that the syntax isn't ambiguous with a variable name.
Snippet variables are a separate concept now.

Resolves #767.

This change fixes some ambiguity in our snippet placeholders to confirm
with stricter parsing rules in VS Code 1.12.0.  Generally this requires
prefixing an index (`${1:Placeholder Text}`) anywhere that a placeholder
is used so that the syntax isn't ambiguous with a variable name.
Snippet variables are a separate concept now.

Resolves PowerShell#767.
@daviwil daviwil added this to the 1.2.0 milestone May 30, 2017
@daviwil daviwil merged commit 0abede3 into PowerShell:master May 30, 2017
@daviwil daviwil deleted the fix-snippets branch May 30, 2017 22:09
@rkeithhill
Copy link
Contributor

Thanks for fixing this.

@daviwil
Copy link
Contributor Author

daviwil commented May 31, 2017

No problem! Wasn't that hard after I figured out how the hell they wanted the placeholders to be formatted ;)

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.

Built-in PowerShell snippets can't be tabbed through
3 participants