Open nickeldan opened 1 week ago
This is expected, you should not be including brackets with the path. The examples show how it should look like in the settings.json
.
Moving this to VS Code to improve how this looks to users. This is example contribution for settings in package json.
@aiday-mar This is a settings rendering issue. Can this be assigned to someone who owns that?
Hi yes thanks @karthiknadig I'll have a look at the working areas md file. I think @sandy081 owns the settings? Assigning to you, let me know if you don't own this code.
@rzhao271 owns the settings editor, moving it to him.
This issue seems specific to the fact that the examples in the setting's description are for users modifying a settings.json
file directly.
I'd rather not change the behaviour of the Settings editor to automatically adjust literal ["textHere"]
entries to textHere
.
@karthiknadig I'm thinking that we can either remove the examples for conciseness or add a separate set of examples for Settings editor users.
For array and object types maybe, we can remove the examples for editor users.
I'm using VSCode 1.92.2 and version v2024.2.0 of the Black Formatter extension. My operating system is macOS (Sonoma 14.6.1). I'm working in a venv virtual environment of Python 3.8.18. I've confirmed that black is installed in my virtual environment.
I noticed that black wasn't being run whenever I saved my files. Looking into, the logs, I saw
Following the instructions in the extension's settings, I had set the black-formatter path to
["black"]
:I tried making the path absolute (
["/Users/user/environments/myproject/bin/black"]
) but got the same error. Finally, I removed the brackets and the quotes (black
) and it worked.