Link to issue number:

Depends on nvaccess/vscode-nvda#1
Closes #9971

Summary of the issue:

Visual Studio Code is currently well known for its accessibility and ease of use. Especially since the NVDA repository has a linting configuration built in, using Visual Studio Code's linter support is pretty handy for non visually working programmers.

Description of how this pull request fixes the issue:

Added a reference in the readme to a preconfigured VSCode workspace. This has to be checked out in the main source directory of NVDA. .gitignore deals with this.

Several settings a configured in this project, see also nvaccess/vscode-nvda#1:

• Accessibility support is enabled
• Linting is enabled based on the Flake8 configuration bundled with the NVDA repository
• Auto complete extra paths are added for the several external submodules
• When saving a file, a final new line is added to it, and extra new lines are trimmed from the end of the file when applicable. This ensures a uniform style across the project
• De default indentation is set to use tabs instead of spaces
• Testing within Code is enabled using the unittest framework

The current NVDA build environment is set up in such a way that it doesn't require a virtual Python environment.
This VSCode project does not define the python interrpetter setting by default.

Testing performed:

Tested that tests run from VS Code and that extra include directories are recognized.

Known issues with pull request:

None

Change log entry:

• Changes for developers
  • The ReadMe of the NVDA development repository now contains instructions on how to use a pre populated workspace configuration for Visual Studio Code for NVDA development. This workspace is configured to use the linting configuration provided with the repository. (Provide VS Code support within NVDA"s git repository #9971)