You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since VSCode doesn't allow environment variables in settings.json files, (see microsoft/vscode#2809), the generated settings.json and .pylintrc aren't very VCS friendly.
To get around this, I think it would be a good idea to generate a symlink (ignored by VCS) at the root of a new project that directs towards the users .micropy folder. This way, once #10 is finished, we can recreate this link when someone else clones the repo and initializes micropy, effectively making the pylint and vscode files VCS friendly.
The text was updated successfully, but these errors were encountered:
Since VSCode doesn't allow environment variables in
settings.json
files, (see microsoft/vscode#2809), the generatedsettings.json
and.pylintrc
aren't very VCS friendly.To get around this, I think it would be a good idea to generate a symlink (ignored by VCS) at the root of a new project that directs towards the users
.micropy
folder. This way, once #10 is finished, we can recreate this link when someone else clones the repo and initializes micropy, effectively making the pylint and vscode files VCS friendly.The text was updated successfully, but these errors were encountered: