A list of concerns to be manually validated as we stabilize project support.
Note: Show Q# Output Window and check for errors/warnings as you do perform the steps.
Debugger:
Debug with single file
Debug with project
Debug with project where files have errors
Try to debug with corrupt qsharp.json
Language service:
Single file:
Type in a single unsaved file, ensure completion list and squiggles are up to date with each keystroke.
Type in a file that's saved to disk. Ensure completion list & squiggles with each keystroke.
Project:
Go-to-definition across files with project
Type in a file that's part of a project. Ensure completion list & squiggles with each keystroke.
Have two open documents for the same project, with edits. Ensure the language service uses the edits from both documents (test with go-to-definition)
Corrupt qsharp.json. Does the user get a warning?
Project updates:
Create two files on disk first. Then, add a qsharp.json in the same folder. Ensure the project is picked up.
Add a new file to an existing qsharp.json project, ensure it is included in the program.
Back to single-file mode:
While file is open in the editor , move it out of the project folder. Through completion list / go-to-definition / errors, confirm that the file is now treated as a single file.
Renames, moves, etc:
Rename the folder that the project is in, see what happens
Move a file from outside the project directory into the project directory.
Rename a single .qs file in a project. Ensure project is still valid - check Problems window and go-to-definition
Add a subdirectory containing .qs files to the project under ./src. Rename it. Ensure consistent state at each step.
QIR generation:
Submit single-file (no qsharp.json) program to Azure
A list of concerns to be manually validated as we stabilize project support.
Note: Show Q# Output Window and check for errors/warnings as you do perform the steps.
./src
. Rename it. Ensure consistent state at each step.