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
Logpoints do not evaluate correctly #1707
Comments
Is this only in Preview? |
@andschwa pretty sure but haven't fully tested, I know it used to work just fine, I've used it before. |
I think you might be remembering wrong. AFAIK this is just a string, so you'd need to use subexpression for properties. Update: Tested in stable and 2021.8.0. No change and If anything I'd consider adding support for |
If {} is present it could just be replaced with $() before being sent to the evaluator. Good call on it being brought in as a string and not a scriptblock, wonder if there's a way to modify the placeholder text per-extension to be more clear on this. |
Will likely have to use AST-parsing to not break expressions with scriptblocks, ex
I can't really see a way to customize it without trying to override using localization, but I doubt we could change language pack depending on document language. I've submitted a feature request (microsoft/vscode#157324) for language-specific syntax in the placeholder-text. |
Expected: The actual value
The text was updated successfully, but these errors were encountered: