-
Notifications
You must be signed in to change notification settings - Fork 27
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
Sync Folder seems to not respected settings.json #214
Comments
i made a test and change the "default" part of the syncFolder configuration in my if i do the setting there it work as excpected. it seems that the settings.json in the .vscode folder in my project folder do not respected. the defaults from package.json do override project setting or it just not loaded. i dont know. same with #213 Chris |
Don't know if this is related, but sync config does not work in multi-folder workspaces. Should I create a new issue? |
yes that is exactly what happen. i think the workspace should change back to single workspace after toggling the pico-filsystem button again. Chris |
This is more of how VSCode extension settings work. IMO this setting should be instead in the However since we have it in the extension setting for now, what you can do is save the VSCode workspace and set the extension settings there:
{
"folders": [
{
"path": "."
},
{
"name": "Pico (W) Remote Workspace",
"uri": "pico:"
}
],
"settings": {
"python.linting.enabled": true,
"python.languageServer": "Pylance",
"python.analysis.typeCheckingMode": "basic",
"python.analysis.typeshedPaths": [
".vscode\\Pico-W-Stub",
"~\\.micropico-stubs\\included"
],
"python.analysis.extraPaths": [
".vscode\\Pico-W-Stub\\stubs",
"~\\.micropico-stubs\\included"
],
"[python]": {
"editor.defaultFormatter": "ms-python.black-formatter"
},
"python.analysis.diagnosticSeverityOverrides": {
"reportMissingModuleSource": "none"
},
"micropico.syncFolder": "src",
"micropico.openOnStart": true,
"micropico.softResetAfterUpload": true
}
} |
What about the other issue mentioned by OP?
The files from src folder should be copied directly into / and not to /src on the device. If the current behaviour was intended (i.e. specifying "src" will copy the whole folder), what about allowing to specify "src/*" as option to relatively create the copies on the device? |
@webdeb Thanks for mentioning. Should be patched with the latest release. It was a scope issue of the settings. @ChrisChoke I guess this should also be fixed with the latest release (v4.1.0), can you confirm? |
settings.json:
What are the steps to reproduce this issue?
What happens?
all .py files on all relative pathes are uploaded to the board.
What were you expecting to happen?
i excpect that the syncFolder perform a
cd src
and upload all files within this folder and apply all rules at this stage.i mean that synFileTypes applied at this folder and subfolder within it.
i excpect that the syncFolder will be at root on filesystem on my board. like if i do
cp src/* /
on linux.Any logs, error output, etc?
(To get extension logs see Terminal > Output > Extension Host and copy output concerning pico-w-go or micropico)
(If it’s long, please paste to https://gist.github.com and insert the link here)
Any other comments?
Which version of MicroPico are you using?
3.7.5
Support info
Copy this from the
Help -> Info/About -> Copy
(Code -> About Visual Studio Code -> Copy
on macOS) option in Visual Studio Code:The text was updated successfully, but these errors were encountered: