With Autosave Off, Preview does not reflect the state of the SOQL Builder UI

[dehru]

OS and version:
Windows 10

VS Code Version:
1.52.1

SFDX CLI Version:
7.82.1

Summary

When autosave is not turned on, the soql preview does not update to represent the actual state of the query. It appears that the onDocumentChange event does not get fired until the file is saved. And then it updates. This can cause confusion since the state of the inputs and the preview do not match. When the query is run, it is run with the soql query that is currently unsaved in the text document.
Short summary of what is going on or to provide context.

Steps To Reproduce:

1. Open a soql query in soql builder
2. Make sure autosave is off in your vscode preferences
3. Adjust the query using the soql-builder form inputs
4. Watch the preview panel of the soql builder is not updated
5. Run the query and watch the results represent the state of the UI ( and the state of the unsaved soql query )
6. Save the file and watch the preview update to reflect the true state of the soql statement.

Expected result

I guess that the soql statement in the preview should align with the state of the UI controls. And the state of the unsaved soql file. It might be nice for the user to know that this preview is not saved. Which could give them confidence to make changes and manipulate their query until they WANT to save the results.

I usually work with autosave on. So I expect the state of the UI, the preview, and the saved file to always be the same. But novice users may prefer to manually control saving the file.

Actual result

UI controls in the soql builder and the preview are not in sync.

Additional information

auto-save-turned-off.mov