Add VSCode folder to gitignore

[MayberryZoom]

Adds a basic settings file, then gitignores the .vscode folder

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.93%. Comparing base (688cc5f) to head (e8e09a9).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #255   +/-   ##
=======================================
  Coverage   76.93%   76.93%           
=======================================
  Files          78       78           
  Lines        3894     3894           
=======================================
  Hits         2996     2996           
  Misses        898      898           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ThanatosGit]

All lines besides "python.testing.pytestEnabled": true, are the default values.
Any reason why they are added?

[MayberryZoom]

So that it works out of the box.

[Miepee]

if the values are default they should work out of the box, no?

[MayberryZoom]

I'm pretty sure the env file isn't default anyways. The rest is auto-generated by VSCode but without declaring the env file it won't work.

[ThanatosGit]

The path for the env file is the default.

[ThanatosGit]

I really can't follow.

I'm pretty sure the pytest enabled setting is added automatically by VSCode when you press the configure tests button then select pytest

That is not

So that it works out of the box.

That is why suggested to

At least values which are different from the default should stay in the file which is only "python.testing.pytestEnabled": true

So, why is it now completely removed?

[MayberryZoom]

When you open up the project in VSCode and go to the tests side bar, if there's no settings.json it will prompt you to configure tests. If you press that button you can select pytest, then it auto generates the settings.json file. That "python.testing.pytestEnabled": true is part of that file. And as you said, so is the env path. So imo there's no need to include that file in the repo.

[dyceron]

Anything holding this pr back?

[ThanatosGit]

Basically me who still doesn't know what's the goal here. If it is to just ignore the settings.json, it's fine.
If it is to work "out of the box", then it's missing stuff.
As already described, without a settings.json, VSCode will prompt you to configure tests but that's a selection between two different frameworks where the wrong one is even described as Standard Python test framework

Eventually there should be at least an example .env file in the README or a .env file with placeholders?

[dyceron]

Well, it'd be nice to figure out so I don't have to keep a settings.json file with changes on every branch I work on.